Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!usc!cs.utexas.edu!uunet!microsoft!keithro
From: keithro@microsoft.UUCP (Keith ROWE)
Newsgroups: comp.lang.c
Subject: Re: Bugs in Microsoft compilers (was: Re: MS C 6.00a bug list)
Message-ID: <71990@microsoft.UUCP>
Date: 22 Apr 91 18:32:41 GMT
References: <8439@umd5.umd.edu> <1991Apr18.070131.1892@unicorn.cc.wwu.edu> <1991Apr18.133035.15827@bronze.ucs.indiana.edu> <11139@uwm.edu>
Reply-To: keithro@microsoft.UUCP (Keith ROWE)
Distribution: usa
Organization: Microsoft Corp., Redmond WA
Lines: 25

>I'm having somewhat similar problems now, after finding a problem in QC2.5's
>incremental linker and object code generation process.  What makes it really
>inaccessible is that they made their object code format proprietary which
>entails a lengthy period of analysis/decoding/reverse-enginerring.  And of
>course, no source is ever distributed.

The MS C 6.0 object code formats, Codeview OMF formats and lots of other
good things are available in the "MS C Developer's Toolkit" (part no.
048-044-060).

Similar extra information on Windows formats are available in the "Windows
Developer's Notebook" (sorry, I don't have the part no. on hand).

Either of these can be ordered through the regular telephone channels.

We also hosted the Open Tools Summit on April 9 and 10 to make the formats
for our next round of language tools available.   The notes from this 
meeting will be available real soon now.

I hope this helps,

Keith Rowe
Program Manager, C Languages
Microsoft
uunet!microsoft!keithro