Re: It works... now what?
- From: Robert Redelmeier <redelm@xxxxxxxxxxxxxxx>
- Date: Tue, 27 Dec 2005 19:23:36 GMT
#2pencil <number2pencil@xxxxxxxxx> wrote:
> The reason (as I understand it) for writing in asm is for efficiency.
But efficiency means different things to different people.
For some it is speed. For others, size. For yet others,
it is simply crisper than going through the virtual machine
presented by compiled languages.
> So for this reason, once a program is finished, then it's time
> to make it work better, faster, & with more efficient code.
Optimization is a _huge_ subject, with asm only a small part
at the end. Please remember Knuth: "Premature optimization
is the root of all evil [code]"
> ; this code opens the windows registry,
> ; replaces the proxy server address,
> ; & then sets enable to 0 or 1
Hmm ... a dubious target for optimization. Will this code
be run often? Are delays intolerable? This sort of code is
normally written for robustness, not speed or size efficiency.
-- Robert
.
- Follow-Ups:
- Re: It works... now what?
- From: hutch--
- Re: It works... now what?
- References:
- It works... now what?
- From: #2pencil
- It works... now what?
- Prev by Date: It works... now what?
- Next by Date: Re: Numeric output
- Previous by thread: It works... now what?
- Next by thread: Re: It works... now what?
- Index(es):
Relevant Pages
|
|
