Re: Introducing "f0dder.lib" and "f0dder.inc" for MASM.
- From: randyhyde@xxxxxxxxxxxxx
- Date: 18 Jul 2005 13:24:52 -0700
Donkey wrote:
> >
> Nope, they have not changed it in later versions, only one model
> directive per program or you get error A4011.
But the issue isn't memory model. It's calling convention. Unless I'm
missing something, somewhere, you can set the calling convention on a
routine by routine basis. Indeed, if I understand the argument
correctly, this is what everyone is suggesting be done to the MASM32
header files. The same trick can apply to user-written routines, no?
For example, HLA's MASM output always sets the memory model to "flat,
syscall". However, by default HLA uses the Pascal calling convention.
Now it may be more *inconvenient* to have to set up all the prototypes
to use a different call, and that would be a valid argument for making
the change to the MASM32 header files, but I still don't see this as a
"bug" or anything like that, just a poor design decision.
As to the issues concerning sleep(0) and other stuff appearing
throughout this thread, I'm assuming that such comments are describing
a completely *different* problem and, not understanding the background
issues, I'm not in a position to comment. For that matter, I'm not even
paying a whole lot of attention to this whole thread, so my
understanding of the problem could be way off, anyway.
Cheers,
Randy Hyde
.
- Follow-Ups:
- References:
- Introducing "f0dder.lib" and "f0dder.inc" for MASM.
- From: hutch--
- Re: Introducing "f0dder.lib" and "f0dder.inc" for MASM.
- From: f0dder
- Re: Introducing "f0dder.lib" and "f0dder.inc" for MASM.
- From: hutch--
- Re: Introducing "f0dder.lib" and "f0dder.inc" for MASM.
- From: Beth
- Re: Introducing "f0dder.lib" and "f0dder.inc" for MASM.
- From: f0dder
- Re: Introducing "f0dder.lib" and "f0dder.inc" for MASM.
- From: randyhyde
- Re: Introducing "f0dder.lib" and "f0dder.inc" for MASM.
- From: f0dder
- Re: Introducing "f0dder.lib" and "f0dder.inc" for MASM.
- From: ararghmail507NOSPAM
- Re: Introducing "f0dder.lib" and "f0dder.inc" for MASM.
- From: Donkey
- Introducing "f0dder.lib" and "f0dder.inc" for MASM.
- Prev by Date: Re: Introducing "f0dder.lib" and "f0dder.inc" for MASM.
- Next by Date: Re: Introducing "f0dder.lib" and "f0dder.inc" for MASM.
- Previous by thread: Re: Introducing "f0dder.lib" and "f0dder.inc" for MASM.
- Next by thread: Re: Introducing "f0dder.lib" and "f0dder.inc" for MASM.
- Index(es):
Relevant Pages
|
Loading