(no subject)

[haberg]

. <address@hidden> <address@hidden>
Mime-Version: 1.0 (Apple Message framework v746.2)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <address@hidden>
Cc: Bison Bugs <address@hidden>,
 Akim Demaille <address@hidden>
Content-Transfer-Encoding: 7bit
From: Hans Aberg <address@hidden>
Subject: Re: too many warnings from Bison CVS for Pike
Date: Thu, 9 Feb 2006 14:08:06 +0100
To: Paul Eggert <address@hidden>
X-Mailer: Apple Mail (2.746.2)

On 9 Feb 2006, at 01:48, Paul Eggert wrote:

>> I guess that if there is, as Akim says, a dedicated effort for the C-
>> parser to compile under C++ in current and upcoming Bison versions,
>
> That's not clear to me.  yacc.c happens to work, but I'd be surprised
> if the yacc.c code actually conforms to the current C++ standard, and
> thus there are no guarantees.  I don't recommend this usage, and I'd
> rather not document it.  People who misuse C++ compilers as if they
> were C compilers tend to know about the issues involved; but it's on
> them to get this to work, and it's their responsibility if it doesn't.

I just gave my impression from the input of Akim:

On 6 Feb 2006, at 09:59, Akim Demaille wrote:

>> If you want to support a compile C as C++ option,
>> contact the developers. The problem is not that it impossible as
>> such, but there is no-one willing to do the job.
>
> This is wrong.  Care is taken, and always has, to make yacc.c
> compilable with a C++ compiler.  Of course you can't expect yacc.c to
> provide classes, use streams, and so on.

My impression is that you is a dedicated C programmer, and do not  
want to work with the C++ stuff in the context of these C skeletons.  
So it suggests that Akim is the one doing an independent effort of  
yours to get these C-skeleton compilers working under at least some C+ 
+ compilers. It suggests some kind of support, though not official.

My own problem is only what to say to people who want to use the  
compile C as C++ option as a part of their projects in some cases  
used by many (as I want to use a C++ skeleton giving me full access  
to C++ features). The statements by you and Akim do not converge in  
my mind, and need some syncing, it seems. :-)

   Hans Aberg