However below you mentioned a possibility for some kind of code
generator, that would work too, it would just mean copying some same
kind of work between the different front-ends.
Motivation for the code generator would be primarily to ease
maintenance. Frontends would then plug into information provided
dynamically OR provide a specific part of the code generator that
emits appropriate code statically.
Hi everyone,
one of the current weaknesses of FreeSCI-- particularly Glutton-- is
the lack of unified configuration handling. While I'm fairly
comfortable with the treatment of configuration files at the moment
(config.l), the following things are lacking:
- Systematic integration of command-line arguments with configuration
file options
- Dynamic configuration updates (as required for reasonable builtin
frontend support)
- Support for a default system configuration file
Beyond this, Gluton's configuration support is fairly incomplete ATM,
but that's something we can pick up along the way there. Now, there
has been some work on front-ends, so I'm wondering: What are the
requirements these systems have? Would it be feasible to generate the
information needed by these systems statically, throught a simple
code-generator?
Thanks in advance for any feedback,
-- Christoph
_______________________________________________
FreeSCI-develop mailing list
address@hidden
http://mail.nongnu.org/mailman/listinfo/freesci-develop