This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: bastring.cc
>>>>> Alexandre Oliva <oliva@dcc.unicamp.br> writes:
> Jason Merrill <jason@cygnus.com> writes:
>>>>>>> Alexandre Oliva <oliva@dcc.unicamp.br> writes:
>>> Jeffrey A Law <law@cygnus.com> writes:
>>>> Is user code supposed to be able to include this file directly?
>>> As Jason, wrote, this is not supposed to work with the current and
>>> correct approach of egcs to include bastring.cc in bastring.h.
>>> Unfortunately, it was necessary to include it on some platforms such
>>> as IRIX 5.2, SunOS 4.1.3 and Cygnus/GNU-Win32, that would not work
>>> without bastring.cc explicitly included in every translation unit that
>>> would require some symbol defined within it.
>> Huh? Why? Why didn't anyone mention this to the g++ team?
> I did, and that's why bastring.h now includes bastring.cc. And I
> suggested a temporary forward-compatible work-around for this problem
> for both guavac and lilypond.
You shouldn't be #including bastring.h, either. <string> is the header you
want.
Jason