assembly and to write a procedure
From: beta (beta_at_s.l)
Date: 07/25/04
- Next message: Daniel.: "Re: HLA v1.68 is now available"
- Previous message: beta : "Re: shift and failure to exceed compiler in speed"
- Next in thread: Phil Carmody: "Re: assembly and to write a procedure"
- Reply: Phil Carmody: "Re: assembly and to write a procedure"
- Reply: wolfgang kern: "Re: assembly and to write a procedure"
- Reply: johnnyb_at_eskimo.com: "Re: assembly and to write a procedure"
- Reply: beta : "Re: assembly and to write a procedure"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Sun, 25 Jul 2004 09:14:24 GMT
When you write a procedure in assembly (e.g. a shift function),
how much time do you pass to write only (without the first run)?
How much time do you pass in the debug stage?
In the 90% have you to correct few errors from the first run?
And in another computer language (e.g. C, or C++ or Basic)?
It seems to me that in C the debug stage is longer.
It seems to me that assembly is very good for find errors (until
without the debugger, but seems, from when I start the use of the
debugger, it is a lot better and faster). Is it right?
- Next message: Daniel.: "Re: HLA v1.68 is now available"
- Previous message: beta : "Re: shift and failure to exceed compiler in speed"
- Next in thread: Phil Carmody: "Re: assembly and to write a procedure"
- Reply: Phil Carmody: "Re: assembly and to write a procedure"
- Reply: wolfgang kern: "Re: assembly and to write a procedure"
- Reply: johnnyb_at_eskimo.com: "Re: assembly and to write a procedure"
- Reply: beta : "Re: assembly and to write a procedure"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|