Re: DDD-3.3.9-test1 is released

[Tim Mooney]

In regard to: Re: DDD-3.3.9-test1 is released, Arnaud Desitter said (at...:

>> In regard to: Re: DDD-3.3.9-test1 is released, Arnaud Desitter said
>(at...:
>>
>> >> On Tru64 5.1b with the vendor C and C++:
>> >>
>> >> Compaq C V6.5-207 (dtk) on Compaq Tru64 UNIX V5.1B (Rev. 2650)
>> >> Compiler Driver V6.5-207 (dtk) (dtk) cc Driver
>> >>
>> >> Compaq C++ V6.5-039 for Compaq Tru64 UNIX V5.1B (Rev. 2650)
>> >> Compiler Driver V6.5-039 (cxx) cxx Driver
>> >>
>> >> I configured with CXXFLAGS that include `-std
>gnu -D__USE_STD_IOSTREAM',
>> >> and get a lot of errors from ddd.C:
>> >
>> >What happen if you drop "-std gnu" ?
>>
>> I just tried it with `-std gnu', without `-std gnu', with `-std ansi', and
>> without `-std ansi'.  It doesn't make any difference.  The exact same
>> errors happen in each case.
>>
>
>Without access to this compiler, I cannot find a solution. Sorry.
>You could derived a stand alone example that reproduces the problem
>and ask in a newsgroup.

I did some more investigation into the problem (compilation of ddd.C
fails like this:

cxx -DHAVE_CONFIG_H -I. -I. -I.  -I./.. -I/local/include -I/local/gnu/include  
-DNDEBUG   -std ansi -O3 -tune host -arch host -Olimit 3000 -readonly_strings 
-D__USE_STD_IOSTREAM -msg_display_tag    -c -o ddd.o ddd.C
cxx: Error: strclass.h, line 464: "string" is ambiguous (ambiguousname)
    const string& S;            // The string I'm a constSubString of
----------^
cxx: Error: strclass.h, line 468: "string" is ambiguous (ambiguousname)
    constSubString(const string& x, int p, int l);
-------------------------^
cxx: Error: strclass.h, line 481: "string" is ambiguous (ambiguousname)
    bool contains(const string& y) const;
------------------------^



and so on).


The compiler is apparently objecting because `string' is a typedef in the
Standard C++ library, for the templated basic_string class:

  typedef basic_string<char, char_traits<char>, allocator<char> >
  string;


Other platforms (Solaris 8, IRIX 6.5.22m) have a similar version of the
`string' header as part of their C++ Standard library (all of them
appear to be derived from Rogue Wave's Standard C++ library, of one
vintage or another), so I'm not sure why they're not having the same
problem.

I'll keep looking for a way around the problem, but at least now I know
where it's coming from.

Tim
-- 
Tim Mooney                              address@hidden
Information Technology Services         (701) 231-1076 (Voice)
Room 242-J6, IACC Building              (701) 231-8541 (Fax)
North Dakota State University, Fargo, ND 58105-5164