Re: Problems with bison.simple and C++

[Akim Demaille]

>>>>> "Adam" == Adam Tee <address@hidden> writes:

>> First, a preliminary question: does your application need to be
>> portable, or should it follow the C++ standard?  The problem is
>> that the standard clearly says size_t is in std, and your
>> environment is wrong on this regard.  Now, we know many environment
>> have still not caught up with the standard...
>> 

Adam> Yes, it has a windows version which is out of date at the moment
Adam> (compiled under CYGWIN), the program is GNU Denemo.  

So you do face a portability problem, hence Autoconf is the only way
out.  I hope the skeleton is flexible enough for you...  Keep us
informed, as 1.32 is already scheduled.  If adjustments are needed for
you, I'd like to make it into 1.32.

Adam> I'm using g++ v3.0.3 to compile it.  

That's really weird: g++ 3 is fairly compliant:

/tmp % cat foo.cc                                                nostromo 11:39
#include <cstdlib>

int
main (void)
{
  std::size_t foo = sizeof (std::size_t);
  return 0;
}
/tmp % g++-2.95 -Wall -ansi foo.cc                               nostromo 11:39
foo.cc: In function `int main()':
foo.cc:6: warning: unused variable `size_t foo'
/tmp % g++-2.95 --version                                        nostromo 11:39
2.95.4
/tmp % g++-3.0 -Wall -ansi foo.cc                                nostromo 11:39
foo.cc: In function `int main()':
foo.cc:6: warning: unused variable `size_t foo'
/tmp % g++-3.0 --version                                         nostromo 11:39
3.0.3


I don't understand your problem.