Re: Fwd: Test Header

[Alexandre Julliard]

Jon  writes:
> Finally, all references to stdout have been removed - this allows the tests
>  to be built with msvcrt or libc and work. This in turn allows developers to
>  check that c library differences (e.g. printf formatting) won't affect the
>  test results, without rebooting to rebuild/re-run the tests under native
>  windows. It also means you can manually call _chkstk when implementing
>  undocumented calls to ensure that you have the parameters and calling
>  convention correct (a coming patch implements this function for builtin
>  msvcrt).
>
> Note we have to define __NO_INLINE__ when we make the tests, since otherwise
> our non-stdout referencing calls get mapped straight back to referencing
> stdout by the glibc headers, and msvcrt will blow up trying to write to a non
> existant fd.

This is wrong; if you link with msvcrt you have to use msvcrt headers,
and then everything works fine, including references to stdout. If you
mix glibc and msvcrt you are in trouble.

Fwd: Test Header

[Jon Griffiths]

Hi,
> This is wrong; if you link with msvcrt you have to use msvcrt
> headers, and then everything works fine, including references to
> stdout. If you mix glibc and msvcrt you are in trouble.

Understood and noted here too - wrong but occasionally useful ;-)

Can you apply the rest of the patch (ie just to the header itself) in
any case? There is no harm in removing stdout references from the
printing, and the verbose option and running all tests is proving
useful here (the number of tests required for the oleaut32 variant
functions is large, and I'm only half way through them).

Cheers,
Jon

=====
"Don't wait for the seas to part, or messiahs to come;
 Don't you sit around and waste this chance..." - Live

[e-mail]

__________________________________________________
Do you Yahoo!?
Yahoo! Platinum - Watch CBS' NCAA March Madness, live on your desktop!
http://platinum.yahoo.com

Fwd: Test Header

[Gregory M. Turner]

On Tuesday 18 March 2003 07:32 am, Jon Griffiths wrote:
> Hi,
> > This is wrong; if you link with msvcrt you have to use msvcrt
> > headers, and then everything works fine, including references to
> > stdout. If you mix glibc and msvcrt you are in trouble.
>
> Understood and noted here too - wrong but occasionally useful ;-)

hmmm... I wonder if I am guilty of this...

Fwd: Test Header

[Gregory M. Turner]

On Tuesday 18 March 2003 07:32 am, Jon Griffiths wrote:
> Hi,
> > This is wrong; if you link with msvcrt you have to use msvcrt
> > headers, and then everything works fine, including references to
> > stdout. If you mix glibc and msvcrt you are in trouble.
>
> Understood and noted here too - wrong but occasionally useful ;-)

would make checklink find this?  could it?

Fwd: Test Header

[Alexandre Julliard]

Jon Griffiths  writes:
> Can you apply the rest of the patch (ie just to the header itself) in
> any case? There is no harm in removing stdout references from the
> printing, and the verbose option and running all tests is proving
> useful here (the number of tests required for the oleaut32 variant
> functions is large, and I'm only half way through them).

Running all tests this way is not a good idea, this was discussed
already.