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

What's the compiler error message you get?


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
>

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
> >
> 
> 

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


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
>> >
>>
>>
>
>

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
> >> >
> >>
> >>
> >
> >
> 
> 

I've now run into a full stop..... I've changed the '__i's to 'i__i' and now:

sc console.cpp -mn -C -WA -S -3 -a8 -c -gf -D_CONSOLE=1 -Ab -Id:\sc\stltemp\STL\port\stlport -oconsole.obj
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
Fatal Error: D:\SC\stltemp\STL\port\test\regression\string1.cpp(32): internal error cg87 1144
Lines Processed: 16360  Errors: 1  Warnings: 0
Build failed

I will have to look at a small stand alone test :<

Any suggestions would be welcome.

On Fri, 16 Mar 2001 12:40:49 GMT, Damian Dixon <damian.dixon@tenetdefence.com> wrote:
> 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
> > >> >
> > >>
> > >>
> > >
> > >
> > 
> > 
> 
> 

ok,

I've written a short console application (listing below).

It appears that '__i' is global to the compiler.

The test does not include any headers and has been kept as short and simple as possible and thus probably will not run.

It does however compile and link.

//-------------------------------------------------------------------------------------------------------------

/*
#include	<stdio.h>
#ifndef _CONSOLE
#include <winio.h>
#endif
#ifdef  _WINIO
#include 	<string.h> // For strcpy
#endif
*/

extern "C" int printf(const char *, ...);

void main(int argc, char *argv[])

{
    /* for Win16 Console Applications, _WINIO is defined */
#ifdef _WINIO
    /* By default, Winio sets the title bar to the exe name, use winio_settitle to change it */
    winio_settitle(__hMainWnd,"i_test");
    /* Your about box by default shows the exe name, you can change it by resetting __szModule
       and passing the reset value to winio_about */
    strcpy (__szModule,"i_test");
    winio_about(__szModule);
#endif

for (int i__i = 0; i__i < 10; i__i++)    // NOTE use of i__i
printf("test %d\n", __i);                  // NOTE use of __i

	printf("i_test application.\n");
	printf("Write your code to do i/o here.\n");

	/* for Win32 Console Applications, _CONSOLE is defined */
#ifdef _CONSOLE
   {
    /* Print a prompt prior to exiting so that you can view output */
    int c;
    printf ("Press Return To Exit: ");
    //c = getc(stdin);
   }
#endif
}
/-------------------------------------------------------------------------------------------------------------

The compiler output is:

sc i_test.cpp -mn -C -WA -S -3 -a8 -c -gf -D_CONSOLE=1 -oi_test.obj
link /CO /NOI /DE /NOPACKF /XN /NT /ENTRY:mainCRTStartup /BAS:4194304 /A:512 @i_test.LNK
ren .\$SCW$.EXE i_test.EXE
\i_test.EXE built
Lines Processed: 21  Errors: 0  Warnings: 0
Successful build


Not sure why the compiler exited with the STL regression tests.

Regards,
Damian


On Fri, 16 Mar 2001 12:40:49 GMT, Damian Dixon <damian.dixon@tenetdefence.com> wrote:
> 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
> > >> >
> > >>
> > >>
> > >
> > >
> > 
> > 
> 
> 

I believe I have traced the '__i' problem to complex.h header.

I can provide a work around by changing use of '__i' within STLport.

I still need to look a little closer at the internal error I was getting once I had changed the '__i' to something else. Though suggestions on probably cause of such an error would be helpfull.

Oh, I've also obtained the ANSI C99 document as a reference, at $18 I thought it was the cheapest way of getting a definitive reference :>

Regards,
Damian

Damian Dixon <damian.dixon@tenetdefence.com> wrote in message news:1106_984747400@dilbert...
> ok,
>
> I've written a short console application (listing below).
>
> It appears that '__i' is global to the compiler.
>
> The test does not include any headers and has been kept as short and
simple as possible and thus probably will not run.
>
> It does however compile and link.
>
>
file://---------------------------------------------------------------------
----------------------------------------
>
> /*
> #include <stdio.h>
> #ifndef _CONSOLE
> #include <winio.h>
> #endif
> #ifdef  _WINIO
> #include <string.h> // For strcpy
> #endif
> */
>
> extern "C" int printf(const char *, ...);
>
> void main(int argc, char *argv[])
>
> {
>     /* for Win16 Console Applications, _WINIO is defined */
> #ifdef _WINIO
>     /* By default, Winio sets the title bar to the exe name, use
winio_settitle to change it */
>     winio_settitle(__hMainWnd,"i_test");
>     /* Your about box by default shows the exe name, you can change it by
resetting __szModule
>        and passing the reset value to winio_about */
>     strcpy (__szModule,"i_test");
>     winio_about(__szModule);
> #endif
>
> for (int i__i = 0; i__i < 10; i__i++)    // NOTE use of i__i
> printf("test %d\n", __i);                  // NOTE use of __i
>
> printf("i_test application.\n");
> printf("Write your code to do i/o here.\n");
>
> /* for Win32 Console Applications, _CONSOLE is defined */
> #ifdef _CONSOLE
>    {
>     /* Print a prompt prior to exiting so that you can view output */
>     int c;
>     printf ("Press Return To Exit: ");
>     file://c = getc(stdin);
>    }
> #endif
> }
>
/---------------------------------------------------------------------------
----------------------------------
>
> The compiler output is:
>
> sc i_test.cpp -mn -C -WA -S -3 -a8 -c -gf -D_CONSOLE=1 -oi_test.obj link /CO /NOI /DE /NOPACKF /XN /NT /ENTRY:mainCRTStartup /BAS:4194304
/A:512 @i_test.LNK
> ren .\$SCW$.EXE i_test.EXE
> \i_test.EXE built
> Lines Processed: 21  Errors: 0  Warnings: 0
> Successful build
>
>
> Not sure why the compiler exited with the STL regression tests.
>
> Regards,
> Damian
>
>
> On Fri, 16 Mar 2001 12:40:49 GMT, Damian Dixon
<damian.dixon@tenetdefence.com> wrote:
> > 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
> > > >> >
> > > >>
> > > >>
> > > >
> > > >
> > >
> > >
> >
> >
>
>

I would like to have that document as well
I guess is also covers C++?!
Where did you get it?

Don't worry, be Kneppie!
Jan



Damian Dixon wrote:

> Oh, I've also obtained the ANSI C99 document as a reference, at $18 I thought it was the cheapest way of getting a definitive reference :>

__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.

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 :-(.

Does the STL port use complex.h? If so, it should change to using oldcomplex.h.

-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
> > >> >
> > >>
> > >>
> > >
> > >
> >
> >
>
>