Re: Naming conventions for skeletons

[Paul Eggert]

> From: Akim Demaille <address@hidden>
> Date: 04 Jun 2002 15:58:27 +0200
> 
> maybe all this is overkill and everybody will be happy with
> %skeleton only, and a table of names in the documentation, such as:
> 
>         yacc.c      the current bison.simple, i.e., the default
>         lalr1.c++   the current bison.c++
>         glalr1.c    the forthcoming skeleton from Paul H.
>         btyacc.c & btyacc.cc if we do swallow BTYacc some day
>         drlr1.c     if Carlos Javier Borges Villalba really makes it.
>         etc.

I like this idea the best of the ones that you mentioned.  It's a bit
tricky, since "yacc.c" is not a C file, but as long as the skeletons
are in a subdirectory I guess it's OK.

A nit: "lalr1.c++" is not a portable POSIX file name.  It might be
better to use "lalr1.cc", as ".cc" seems to be the most common GNU
convention for C++ file names.  (Admittedly this is a bit of a
contentious subject.)