Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uwm.edu!linac!att!att!cbnewsi!krb
From: krb@cbnewsi.att.com (karl r barnhardt)
Newsgroups: comp.os.msdos.programmer
Subject: Re: MASM 6.0 and cross-reference listings
Message-ID: <1991Jun25.123241.23397@cbnewsi.att.com>
Date: 25 Jun 91 12:32:41 GMT
References: <jcmorris.677792764@mwunix.mitre.org>
Organization: AT&T Bell Laboratories
Lines: 33

From article <jcmorris.677792764@mwunix.mitre.org>, by jcmorris@mwunix.mitre.org (Joe Morris):
> Unfortunately, one of the changes in MASM 6 is that there is no way to
> get a printed symbol cross-reference table.  The CREF command is gone,
> and the purported replacement for it is the "source code browser" which
> supports interactive examination under the Programmer's WorkBench.
> 
> The first response from Microsoft tech support was that the cross-reference
> listing was now part of the main .LST output produced by ML.  Wrong; the
> listing is in exactly the same format as was produced by MASM 5.1.  The
> tech on the other end of the phone wire apparently thinks that a 
> listing of symbols with values but without any information about where
> they are used is a "cross-reference" listing.
> 
> After we got that straightened out and the phone bill went up another few
> dollars he finally agreed that MASM 6 will not generate a printed xref
> listing under any conditions.  His statement was that Microsoft assumed
> that everybody did all their work while sitting at a PC, and that there
> was no need for a printed listing of symbol usage.
> 
> He never did explain why this wasn't spelled out in the documentation.
> 
> 
> Joe Morris

Another thing about MASM 6.0 is that there is no way to generate line
numbers in an assembly listing. I too called the Microsoft help line
(hotline), and was also placed on hold for 15 minutes while someone
tried to figure out what directive generated line numbers. The final
answer was, "There is no way." I guess if they don't generate a cross
reference listing there is no need for line numbers in the assembly
listing. I'll keep using MASM 5.01 till this bug is fixed.

Karl Barnhardt