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.

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".


Tell me what do you think prior to do anything. Otherwise it's fine.


Regards,
Javi.


On jue, 2005-11-03 at 17:40 +0100, Marco Pantaleoni wrote:
> On Thursday 03 November 2005 16:34, Marco Pantaleoni wrote:
> >
> > If you like, I'll add a command line switch to jal to invoke automatically
> > the preprocessor, thus avoiding the two separate commands shown above.
>
> I've added that switch. Now if you run jal with the "-P" switch, it will
> invoke cpp for you.
> Compiling the example of the previous message would become:
>
> $ jal -P silly-example.jal
>
> (jal will call cpp handling automatically the temporary file creation and
> removal).
>
> You can also specify a different "cpp" passing a command string to -P, as in:
>
> $ jal -P/usr/local/bin/cpp silly-example.jal
>
> you can pass complex commands quoting with simple or double quotes the
> command:
>
> $ jal -P'/usr/local/bin/cpp -funny' silly-example.jal
>
> I can't check if CVS has been updated recently (it goes in time-out right
> now), so I'm providing a patch against the CVS version without my previous
> patch. In other words, this patch supersedes the previous one.
>
> Cheers,
> Marco
>