You havnt truly lived until you have tried to unravel obfuscated C. :-)
One thing I find really helpful is assert/reached macros in assembler that can
test/verify and halt the execution on fail condition (source filename/line
number),
allows for bugs to be keep at minimum.
Sonethimes I think programmers forget to document the function code in english
prior to implementation then they go onto other parts of program thus leaving a
mess for someone else that come along.
>It is always better to go from design to code instead of vice versa
>or just plain code.
Officially one is supposed to make flowcharts/state machines/UML references
ahead of time before forging out a single line in instructions. But, I find
that tedious for small projects so tend to end up write quick pseudocode so I
know how it going to go.
I found that discussion interesting though. thx.
--chris
http://nxdos.sourceforge.net/
someone <[EMAIL PROTECTED]> wrote:
---------------------------------
Get the Yahoo! toolbar and be alerted to new email wherever you're surfing. -------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user
