On Sat, 17 Mar 2001 20:41:00 -0800, "Walter" <walter@digitalmars.com> wrote:
> I have found & fixed a couple problems in the complex number support. If you want, I can email the test compiler to you, to see if the internal error still appears.
> 

yes please.

> In general, I still think there must be an __i in the STL source there somewhere that's screwing things up.
> 

I agree. I'm just doing a find and grep on the STL port source code to see if I missed something.

> -Walter
> 
> 
> Damian Dixon wrote in message <98v6dh$1264$1@digitaldaemon.com>...
> >Walter <walter@digitalmars.com> wrote in message news:98ueip$llf$1@digitaldaemon.com...
> >> __i is a new keyword added to the compiler. It is there to support
> >imaginary
> >> numbers, and is the imaginary number 1, and is evidently the main source
> >of
> >> the difficulties you are having.
> >>
> >
> >yep....
> >
> >> Keywords starting with __ and with _ followed by an uppercase letter are reserved for the implementation. STL seems to think that __ identifiers
> >are
> >> reserved to itself :-(.
> >>
> >
> >I know, sadly enough not every one follows the guidelines. I think it is a carry over from the fact that SGI wrote most of the original implementation for thier compiler and made the work available to others.
> >
> >Hence why I ran the regression tests to see what would happen.
> >
> >If you want to let me know by email when a new version of the compiler is out and I will look at running STL port through the regression tests ASAP.
> >
> >I tend to sometimes have too many distractions to always check the newsgroup :< for announcments.
> >
> >> Does the STL port use complex.h? If so, it should change to using oldcomplex.h.
> >
> >Probably. I need to check. STL port may also provide its own verison of complex. If it does then the header will more then likly be names 'complex' rather then 'complex.h'
> >
> >Damian
> >>
> >> -Walter
> >>
> >>
> >> "Damian Dixon" <damian.dixon@tenetdefence.com> wrote in message news:1104_984746449@dilbert...
> >> > On Fri, 16 Mar 2001 01:12:44 -0800, "Walter" <walter@digitalmars.com>
> >> wrote:
> >> > > The new keywords were the problem last time. To get the preprocessor
> >> output,
> >> > > use the -e -l switches in combination and look at string1.lst.
> >> > >
> >> > > -Walter
> >> > >
> >> > Have done this.... nothing looks out of place though the listing has
> >> rather less in it then I had expected.
> >> >
> >> > However I have found that if I replace the use of '__i' with say 'i__i'
> >> the problem goes away. Guess :>
> >> >
> >> > Seems odd to me and the listing does not show any use of '__i'.
> >> >
> >> > I have never liked using '__' in front of variables. But in this case
> >not
> >> much can be done.
> >> >
> >> > I will do a straight forward hack and replace '__i' with 'i__i' for
> now.
> >> >
> >> > If I have time I will try a small program without STL to see if I can
> >> isolate the problem.
> >> >
> >> > Regards,
> >> > Damian
> >> >
> >> > >
> >> > > Damian Dixon wrote in message <1104_984729166@dilbert>...
> >> > > >On Thu, 15 Mar 2001 10:17:41 -0800, "Walter"
> <walter@digitalmars.com>
> >> > > wrote:
> >> > > >> What's the compiler error message you get?
> >> > > >>
> >> > > >>
> >> > > >
> >> > > >sc
> >> > >
> >>
> >regression\string1.cpp -mn -C -WA -S -3 -a8 -c -gf -D_CONSOLE=1 -Ab -Id:\sc
> \
> >> > > stltemp\STL\port\stlport -oregression\string1.obj
> >> > > >Error: d:\sc\stltemp\STL\port\stlport\stl/_iterator_base.h(387): ')'
> >> > > expected
> >> > > >Error: d:\sc\stltemp\STL\port\stlport\stl/_iterator_base.h(393): ')'
> >> > > expected
> >> > > >Error: d:\sc\stltemp\STL\port\stlport\stl/_iterator_base.h(405): ')'
> >> > > expected
> >> > > >Error: d:\sc\stltemp\STL\port\stlport\stl/_iterator_base.h(406):
> >> > > template-argument '_Distance' not used in function parameter types
> >> > > >Fatal Error:
> >d:\sc\stltemp\STL\port\stlport\stl/_iterator_base.h(414):
> >> too
> >> > > many errors
> >> > > >Lines Processed: 2729  Errors: 5  Warnings: 0
> >> > > >Build failed
> >> > > >
> >> > > >
> >> > > >This is the regression test in the STLport archive
> >> 'port/test/console.prj'
> >> > > .. No changes to the source or project settings other then setting
> the
> >> > > include path.
> >> > > >
> >> > > >I'm still looking at the problem, though time is rather short as I
> am
> >> > > running a week late on final delivery of a large project.
> >> > > >
> >> > > >I was going to look to see if any of the new keywords introduced
> were
> >> > > causing a name clash first, the next step was to look at preprocessor output. One of the problems with most portable
> >> > > >versions of STL is the use of macro's to change behaviour of the
> >> method's,
> >> > > templates etc... to suit a particular compiler. This can make it very difficult to figure out exactly what is going on,
> >> > > >requireing the pre-processor output to be examined.
> >> > > >
> >> > > >I'll probably have some time on Sunday to have a look more deeply.
> >> > > >
> >> > > >Regards,
> >> > > >Damian
> >> > > >
> >> > > >> Damian Dixon wrote in message <1103_984661516@dilbert>...
> >> > > >> >Hi,
> >> > > >> >
> >> > > >> >I've just downloaded the new compiler and have tried to compile
> >the
> >> > > >> regression tests for STLport 4.0 (the version currently in cvs).
> >> > > >> >
> >> > > >> >I'm sorry to report that the tests did not compile.
> >> > > >> >
> >> > > >> >I will try to figure out what may be causing the problem and
> >update
> >> the
> >> > > >> version in cvs as soon as I can.
> >> > > >> >
> >> > > >> >In the mean time if anyone has any fixes could you either post
> >them
> >> or
> >> > > >> email them to me if you don't have access as a commiter to cvs.
> >> > > >> >
> >> > > >> >Regards
> >> > > >> >Damian
> >> > > >> >
> >> > > >>
> >> > > >>
> >> > > >
> >> > > >
> >> > >
> >> > >
> >> >
> >> >
> >>
> >>
> >
> >
> 
>