Re: Slow nasm
- From: Keith Kanios <keith@xxxxxxxxxx>
- Date: Sat, 27 Oct 2007 15:39:03 -0700
On Oct 27, 5:26 pm, Frank Kotler <fbkot...@xxxxxxxxxxx> wrote:
that code
looks to me like it was written by someone who used the macros without
really understanding 'em. I'd be willing to bet that's where the problem
lies.
That was my point, entirely :)
As I've said before, I've used nagoa+.inc. It is actually one of the
things that fueled my desire to see NASM32 through, but as a more
solid and stable approach. Even the initial releases of NASM32 used
ALINK. So those who think that NASM32 is trying to compete with
MASM32, by any resemblance whatsoever... well... they now know the
cost of ignorance ;)
.
- Follow-Ups:
- Re: Slow nasm
- From: volcano
- Re: Slow nasm
- References:
- Slow nasm
- From: volcano
- Re: Slow nasm
- From: santosh
- Re: Slow nasm
- From: Herbert Kleebauer
- Re: Slow nasm
- From: Betov
- Re: Slow nasm
- From: Herbert Kleebauer
- Re: Slow nasm
- From: Betov
- Re: Slow nasm
- From: Herbert Kleebauer
- Re: Slow nasm
- From: Betov
- Re: Slow nasm
- From: Keith Kanios
- Re: Slow nasm
- From: Frank Kotler
- Slow nasm
- Prev by Date: Re: Skybuck's Wolfram (Turing-Like) Machine implementation
- Next by Date: Open the CD-ROM
- Previous by thread: Re: Slow nasm
- Next by thread: Re: Slow nasm
- Index(es):