On Monday 07 November 2005 17:41, Javier Martinez wrote:
> Hi Marco,
>
> Sorry, I've been busy. ;)
>
> Just 2 questions.
>
> The main one: seems that needs an external C preprocessor, isn't it?
> This will be useless for 95% of JAL users, and this will give us a lot
> of problems about this.

Yes, but if someone doesn't need it, he can just ignore it.

One possible solution could be to selective enable the preprocessor support
when running the "configure" script, if called with an "--enable-cpp" switch.
What do you think about this?

> The second one, just a thought: looks like C too much, is there a way
> to "JALify" it? I'm thinking in something like a procedure/function
> syntax: "macro ( ) is ... end macro".

This of course would be the best solution, but I suspect it would require
non-trivial changes to the parser. If jal could parse from a string (starting
from an arbitrary point in the original file, and resuming to the same point
afterwards), it would be quite easy to do, but I doubt it has this
functionality.
I'll try to think if I can envision a solution, but someone with a deeper
understanding than mine of the jal parser could give better indications.

Ciao,
Marco

--
Marco Pantaleoni

elastiC language developer
http://www.elasticworld.org