Re: Masm32 error line number limit
- From: "rhyde@xxxxxxxxxx" <spamtrap@xxxxxxxxxx>
- Date: 26 Apr 2007 09:32:56 -0700
On Apr 24, 3:26 am, spamt...@xxxxxxxxxx (Gerard Bok) wrote:
On 23 Apr 2007 16:30:36 -0700, "r...@xxxxxxxxxx"
<spamt...@xxxxxxxxxx> wrote:
On Apr 23, 1:10 pm, spamt...@xxxxxxxxxx (Gerard Bok) wrote:
On Mon, 23 Apr 2007 12:36:18 GMT, NoS...@xxxxxxxxxxx (Bob Masta)
wrote:
It appears that Masm32 error reports
(to console, anyway) are unable to show
source code line numbers higher than 65535.
I'm guessing this must be a holdover from 16-bit days.
Of course, I *could* insert all new (possibly buggy)
code earlier in the source <g>, but I'm wondering if
there is a way to enable longer line numbers.
I couldn't find any likely suspects in the command
line parameter list.
How about limiting your sources to (well below :-) 65.000 lines
and use the include statement ?
Works great unless your source code files are machine generated. I ran
into this very problem a few years back. It's pretty easy to exceed
the limit when making heavy use of macros in an HLA program of
relatively modest size, for example.
Sounds like you need to locate the guy who wrote HLA and get him
to include and include option :-)
I think you missed the fact that the code was machine-generated by
macros.
Fundamentally, trying to have those macros emit code to different
files wasn't practical.
hLater,
Randy Hyde
.
- References:
- Masm32 error line number limit
- From: Bob Masta
- Re: Masm32 error line number limit
- From: Gerard Bok
- Re: Masm32 error line number limit
- From: rhyde@xxxxxxxxxx
- Re: Masm32 error line number limit
- From: Gerard Bok
- Masm32 error line number limit
- Prev by Date: Re: Mov question
- Next by Date: Re: [SSE] Your technique for loading a float3 and padding it with another float?
- Previous by thread: Re: Masm32 error line number limit
- Next by thread: Re: Masm32 error line number limit
- Index(es):
Relevant Pages
|
Loading