Today I am again thinking about how the extensible grammar facility of Felix can be made more useful.
We now have a rich set of operators in lib/grammar/texsyms.flxh. To make sets useful, for example, we'd need a class (so all the comparisons are connected as for the < > <= etc comparisons). But the grammar is defined elsewhere. not very modular. I need a better processing model. It's also a bit painful: with include "file", open class-name, really needed in each file using it, but to make the code look clean all that's put in the __init__ file (std/__init__.flx) etc. The current "core" packaging concept is managed by config/*.fpc database and flx_pkgconfig. A bit loathe to extend this too much or we end up like Eiffel with a completely separate, powerful, configuration management language. I have resisted using directory structure (e.g. to get the whole std lib you would include "std/_init_" not "std", unlike Ocaml files aren't modules they're just files, etc. -- john skaller skal...@users.sourceforge.net ------------------------------------------------------------------------------ Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't need a complex infrastructure or vast IT resources to deliver seamless, secure access to virtual desktops. With this all-in-one solution, easily deploy virtual desktops for less than the cost of PCs and save 60% on VDI infrastructure costs. Try it free! http://p.sf.net/sfu/Citrix-VDIinabox _______________________________________________ Felix-language mailing list Felix-language@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/felix-language
