libio/strfile.h

libio/strfile.h

[Fred Richardson (at home)]

Hi-

After installation, I found that the macro __PMT used in strfile.h was
never defined causing a parse error at these two lines:  

  typedef void *(*_IO_alloc_type) __PMT ((_IO_size_t));
  typedef void (*_IO_free_type) __PMT ((void*));


                -Fred

Re: libio/strfile.h

[Jeffrey A Law]

  In message < 199808171137.HAA14573@frichard.bbn.com >you write:
  > Hi-
  > 
  > After installation, I found that the macro __PMT used in strfile.h was
  > never defined causing a parse error at these two lines:  
  > 
  >   typedef void *(*_IO_alloc_type) __PMT ((_IO_size_t));
  >   typedef void (*_IO_free_type) __PMT ((void*));
  > 
I believe this was recently fixed (libio/ChangeLog):

1998-08-17  Ulrich Drepper  <drepper@cygnus.com>

        * strfile.h: Define __PMT if not already defined.

Re: libio/strfile.h

[Jeffrey A Law]

  In message < 199709211916.PAA02336@jfc. >you write:
  > 
  > libio has an internal header named strfile.h.  I tried to use g++ to
  > build a program which had its own file named strfile.h.  The program's
  > strfile.h was found instead of the compiler's.  strfile.h is not
  > specified in the draft ANSI C++ standard; nonstandard filenames should
  > have some compiler or library unique prefix (<libio/strfile.h>,
  > <g++-strfile.h>) to avoid this kind of problem.
I've forwarded this to Ulrich since he's officially the maintainer
of libio/libstdc++.

Hopefully he'll have something to say about it soon :-)

Jeff

libio/strfile.h

[John Carr]

libio has an internal header named strfile.h.  I tried to use g++ to
build a program which had its own file named strfile.h.  The program's
strfile.h was found instead of the compiler's.  strfile.h is not
specified in the draft ANSI C++ standard; nonstandard filenames should
have some compiler or library unique prefix (<libio/strfile.h>,
<g++-strfile.h>) to avoid this kind of problem.