Hello.
> Hi, > >> This patch adds support for the Algol 68 programming language to >> Autoconf. It is based on the Algol 68 GCC front-end > [..] >> This WIP seems to work well for me, but almost certainly I am doing >> something wrong, so comments are welcome. > > As I know nothing about Algol 68 or its implementations, my only real > question is: will this work with any other Algol 68 compilers? The only other working Algol 68 compiler is algol68toc, which is a translator to C. It is not maintained, and it implements a sub language of Algol 68. > Note that the GNU coding standards say that if the program variable > is named GA68, then the corresponding -FLAGS variable should be named > GA68FLAGS (with CFLAGS, LFLAGS and YFLAGS being historical exceptions > to this rule). Oh, I didn't realize that. > Probably A68 and A68FLAGS make the most sense though (as if "G" is > for "GNU" we probably shouldn't be baking that into portable configure > scripts today). Sure, I will change it to A68. Thanks.
