[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Bison 1.28b (fwd)

From: Hans Aberg
Subject: Re: Bison 1.28b (fwd)
Date: Sun, 5 Aug 2001 12:50:34 +0200

At 12:20 +0000 2001/08/05, marc-alexandre autret wrote:
>> My compiler has defaults for C++ .cc, .cp, .cpp, .c++ file extensions, but
>> headers use .h or no extension.
>ok, Here is a real problem, I understand now why you do not want this
>It motivate the implementation of your idea (%header_extension %....)
>What is the name of your compiler ? (by curiosity)

I use a Metrowerks CodeWarrior Pro 5 for MacOS pre-X, but there is a later
version Pro 6 available, and I do not know whether even that one is to be
considered up-to date, because MacOS X has a different object code format
(called MachO or something).

Under MacOS, it was common to use C++ .cp files, but I use .cc files. I
decided to use .h headers for C++ files not making use of namespaces, and
no extension for those that do have namespaces. But I am not entirely sold
onto that system: file extensions are good.

But, as far as I know, the C++ standard does not have any recommendations
on that file extension issue (just as the standard headers need not be
implemented as files or be files at all), so I think that one will see a
blend of possibilities.

>Ok. but it bring more informations without opening the grammmar file.

It is still possible to use startup arguments.

> It's the
>goal of extensions.

One should only have the information in the file extension if it is not
possible to have it elsewhere. It is generally a bad practise to have
information about a file external to the file, as it may become lost when
transported over the Internet. So the tendency is to put all information in
the files for that reason. Then use startup arguments if it is needed in
order to give program like "make" flexibility.

  Hans Aberg

reply via email to

[Prev in Thread] Current Thread [Next in Thread]