[repost]Eorros for me, in the assembly history
- From: "¬a\\/b" <al@xxx>
- Date: Wed, 04 Jan 2006 11:42:32 +0100
This is what i think; the errors for the assembly people
in order of importance:
0) Think that "while", "for" "if" etc are better than jumps
1) Do not use multiple instruction for line
(So the instruction string has to be smallest so a=eax etc
and think on minimize the istruction lay-out)
2) Do not use indentation
3) Want to use more than 1000 different instructions without think it
is better reduce that in 20-30. And so not have a good
understanding of code of others assembly programmers because there
is not common way of write some thing
3Bis) (don't know if this 'fit'; don't know if this is right)
use more than 10 different assembly syntax without think it
is better reduce that in 2-3
4) Do not use {} for underline code of the same level
5) Do not have some standard library for every sys cross-OSes
(may be C library could be ok)
6) Think that assembly is a language that can hold good every
problem
7) Do not use heavy "heap memory" and the memory control functions
or something that can find errors in an executable when the
program run.
sono un megalomane?
.
- Follow-Ups:
- Re: [repost]Eorros for me, in the assembly history
- From: Jonathan Bartlett
- Re: [repost]Eorros for me, in the assembly history
- From: randyhyde@xxxxxxxxxxxxx
- Re: [repost]Eorros for me, in the assembly history
- From: \\\\\\o///annabee
- Re: [repost]Eorros for me, in the assembly history
- Prev by Date: Re: Pick the odd one out.
- Next by Date: Re: Trivia Question
- Previous by thread: Trivia Question
- Next by thread: Re: [repost]Eorros for me, in the assembly history
- Index(es):