> > 1. Macro's can never extend or change the real functionality /
> > performance of the compiler. This would imply that a macro-machine
> > should always or best be implemented as a pre-processor.
>
> I agree, but while on unix-like systems a pre-processor is (almost) always
> present, on other systems (windows), it is not. I'm not interested in windows
> personally, but someone else could be, and maybe they don't want to install a
> third-party program.
Marco, you hit in the bulls eye. Ask in the jallist how many of them
have a C compiler to build latest JAL sources ....
... and now think that we're asking them to have a C preprocessor to
daily work with JAL.
As a starting position (just begin to do something), we can place
your code as a patch of latest sources. If I recall well, SF.net have a
special entry for this purposes.
Hi, I've added support to jal for cpp-like preprocessors (cpp, gpp, ...). This essentialy allows to write macros using #define (and correctly handle line...
... Hi Javier, I apologize for the late answer, but I've been out of town. ... of course. The main use of preprocessor support in jal is to write macros, short...
... 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: $...
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...
... 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...
Hi Marco, ... Yes, but what about sharing code? These macro functions will make JAL "other" language (JAL-cpp vs JAL), that is you'll not able to share code ...
... You are right, it would impede code sharing. I think of this feature as a "sharp knife", to be used exclusively when unavoidable, but I understand that ...
... hello Marco, Javi, As a non-C-programmer, I cann't understand the full extend / consequences of this C-isch macro implementation, but here a few remarks: ...
... I agree, but while on unix-like systems a pre-processor is (almost) always present, on other systems (windows), it is not. I'm not interested in windows ...
Hi all, ... Marco, you hit in the bulls eye. Ask in the jallist how many of them have a C compiler to build latest JAL sources .... ... and now think that...
... Yes, I understand. ... This sounds great! Thanks. In the meantime I'll try to come to a more integrated solution. I'll keep you posted. Cheers, Marco -- ...
Hi all, Available patches in jal.sf.net: ID Summary 1352435 10Fxxx support 1352433 Preprocessor support 1118846 JAL 16F648 Extensions Regards, Javi....