Re: assembly and to write a procedure
From: Phil Carmody (thefatphil_demunged_at_yahoo.co.uk)
Date: 07/26/04
- Next message: f0dder: "Re: PRIMES comparision"
- Previous message: Phil Carmody: "Re: f0dder's fabulous folly."
- In reply to: beta : "Re: assembly and to write a procedure"
- Next in thread: Randall Hyde: "Re: assembly and to write a procedure"
- Reply: Randall Hyde: "Re: assembly and to write a procedure"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: 26 Jul 2004 20:36:51 +0300
beta <beta@s.l> writes:
> On 25 Jul 2004 22:22:13 -0700, johnnyb@eskimo.com wrote:
> >For me, assembly language procedures spend most of the time in the
> >debugger. For me, assembly language is more prone to completely stupid
> >errors than other languages, but less prone to large-scale errors. The
> >reason being that saying %ecx when you meant %edx can happen easily,
>
> worse %ebx ...and %edx
> the names are too similar
Visually, yes.
However, c & d are next to each other on the keyboard though.
esi & edi have s & d next to each other too.
I've occasionally forgotten whether my datum was in edi or edx,
which is embarassing.
Phil
-- 1st bug in MS win2k source code found after 20 minutes: scanline.cpp 2nd and 3rd bug found after 10 more minutes: gethost.c Both non-exploitable. (The 2nd/3rd ones might be, depending on the CRTL)
- Next message: f0dder: "Re: PRIMES comparision"
- Previous message: Phil Carmody: "Re: f0dder's fabulous folly."
- In reply to: beta : "Re: assembly and to write a procedure"
- Next in thread: Randall Hyde: "Re: assembly and to write a procedure"
- Reply: Randall Hyde: "Re: assembly and to write a procedure"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|