I just published recent overview of wxWindows for MSW building system. For
now DMC is also included in test suit. See
http://www.abx.art.pl/wx/cleaning.html
Further notes: http://lists.wxwindows.org/cgi-bin/ezmlm-cgi?5:sss:43961

Walter, I'm sure you have some test suit you use before releasing new DMC. I wonder if you could include wxWindows main library building test into it. wxWindows support is kind of official in both directions (DMC makefiles in bakefile system of wxWindows, wxWindows dedicated group on DMC news server) therefore stable working of every new DMC main release is worth enough. Simple, if building wxWindows is possible then release new version. If not possible then release beta version with info to this group so some volounteer could prepare minimal bug report for further investigation.

?

ABX

"W³odzimierz Skiba" <abx@abx.art.pl> wrote in message news:c0t1mq$6qr$2@digitaldaemon.com...
> I just published recent overview of wxWindows for MSW building system. For
> now DMC is also included in test suit. See
> http://www.abx.art.pl/wx/cleaning.html
> Further notes: http://lists.wxwindows.org/cgi-bin/ezmlm-cgi?5:sss:43961
>
> Walter, I'm sure you have some test suit you use before releasing new DMC. I wonder if you could include wxWindows main library building test into
it.
> wxWindows support is kind of official in both directions (DMC makefiles in bakefile system of wxWindows, wxWindows dedicated group on DMC news
server)
> therefore stable working of every new DMC main release is worth enough. Simple, if building wxWindows is possible then release new version. If not possible then release beta version with info to this group so some volounteer could prepare minimal bug report for further investigation.
>
> ?
>
> ABX

8.39 tightened up the member access rules to be C++98 standard conformant. I'll check out the example you posted.

All new betas are announced in the c++.beta group; I apologize if that was not sufficient.

I'm interested if there is a canonical example for the linker problems you're experiencing.

"Walter" <walter@digitalmars.com> wrote in news:c0to3n$1f2g$1@digitaldaemon.com:
> All new betas are announced in the c++.beta group; I apologize if that was not sufficient.

That's sufficient for me. It is just that some users are wary about products marked "beta". They prefer to download latest full release if they want it in some closed development. I agree Open Watcom, Borland, VisualC and others does not have wxWindows in their regression tests but their teams does not release new versions as often as you.

> I'm interested if there is a canonical example for the linker problems you're experiencing.

I'm affraid I have no idea how :-(
As I mentioned in report at c++.command-line group, this is not replicable
problem. I run 130 builds in one batch and it crashes or hangs for
different builds in one run, and different for another. The only thing I
know is that if it hangs, I can break it with Ctrl+C and continue my batch
so my test suit can be continued. When it crashes I can click on
termination window and my batch continue too. Perhaps some other people who
confirmed my problem in c++.command-line could be more helpful.

Anyway new 8.40 beta gave me another bug report for you which was in 8.39 and perhaps earlier too. When I compiled FL contrib of wxWindows with

dmc -mn -c -odmc_msw\fllib_rowlayoutpl.obj -o -D__WXMSW__ - I..\..\src\fl\..\..\..\include -I..\..\src\fl\..\..\..\lib\dmc_lib\msw  -w- -I..\..\src\fl\..\..\include -Ar -Ae   ../../src/fl\rowlayoutpl.cpp

I got:

                     );
                    ^
../../src/fl\rowlayoutpl.cpp(264) : Error: ')' expected

I truncated the problem down and here it is:
  - None of above switches influence error. I could duplicate it with
       dmc rowlayoutpl.cpp
  - minimal code where problems seems duplicated is:

       double x;

       #define wxMax(a,b) (((a) > (b)) ? (a) : (b))

       void proc( void )
       {
           wxMax( x, int( double(freeSpc) * pcntSum ) );
       }

    It returns me:

        wxMax( x, int( double(freeSpc) * pcntSum ) );
                                                  ^
        rowlayoutpl.cpp(7) : Error: ')' expected

    note for shorter code freeSpc and pcntSum are not declared but their
    declaration does not change problem

ABX

"W³odzimierz Skiba" <abx@abx.art.pl> wrote in message news:c10bpi$2oh0$1@digitaldaemon.com...
> Anyway new 8.40 beta gave me another bug report for you which was in 8.39 and perhaps earlier too. When I compiled FL contrib of wxWindows with
>
> dmc -mn -c -odmc_msw\fllib_rowlayoutpl.obj -o -D__WXMSW__ -
>
..\..\src\fl\..\..\..\include -I..\..\src\fl\..\..\..\lib\dmc_lib\msw  -w-
> -I..\..\src\fl\..\..\include -Ar -Ae   ../../src/fl\rowlayoutpl.cpp
>
> I got:
>
>                      );
>                     ^
> ../../src/fl\rowlayoutpl.cpp(264) : Error: ')' expected
>
> I truncated the problem down and here it is:
>   - None of above switches influence error. I could duplicate it with
>        dmc rowlayoutpl.cpp
>   - minimal code where problems seems duplicated is:
>
>        double x;
>
>        #define wxMax(a,b) (((a) > (b)) ? (a) : (b))
>
>        void proc( void )
>        {
>            wxMax( x, int( double(freeSpc) * pcntSum ) );
>        }
>
>     It returns me:
>
>         wxMax( x, int( double(freeSpc) * pcntSum ) );
>                                                   ^
>         rowlayoutpl.cpp(7) : Error: ')' expected
>
>     note for shorter code freeSpc and pcntSum are not declared but their
>     declaration does not change problem
>
> ABX

I'll check it out. For the moment, try using the old style cast for the
int() and double().