C syntax errors
frank kolmann <[email protected]>
| Newsgroups | gmane.comp.lang.as400.c |
|---|---|
| Message-ID | <CAB-SQvhYyX=BSNHMH3B58zBp6xw2Lb-DMxU8=qhiNFfbmEUpYg@mail.gmail.com> |
Hi Paul Thank you for the information. Yes I also have long ago learnt the principle of keep the code blocks small enough to fit on one page. (Modern monitors allow a bit too many lines) I have never had to compile repeatedly using stubs to link to functions, procedures not yet coded. But now it is very clear why and how one would need to code this way and compile repeatedly. I am making some progress with K&R exercise 5.20, If I ever get it working I will post it and see the feedback. (I am prepared to be embarrassed) Regards Frank Kolmann >date: Mon, 20 Jan 2014 12:04:29 +0100 >from: [email protected] >subject: Re: [C400-L] C syntax errors > >Hi Frank > >When you suggest to use small fragments, I think you are on the right >way... but for me, this is independant of the language... >I try to never write a program/sub program/subroutine/paragraph/function >longer than 20 lines... (my guideline is "do not use roll up/PageDown >key") >and I do not spare computer time : I invoke the compiler at every new >routine... It ensures that any syntax problem is is my last 20 lines of >code.... > >of course when you write very low level code (drivers, encryption, etc... >) performance must be considered ,but optimization is a next step. > > >Kind Regards, thank you, >Paul -- This is the Bare Metal Programming IBM i (AS/400 and iSeries) (C400-L) mailing list To post a message email: C400-L-Zwy7GipZuJhWk0Htik3J/[email protected] To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/c400-l or email: C400-L-request-Zwy7GipZuJhWk0Htik3J/[email protected] Before posting, please take a moment to review the archives at http://archive.midrange.com/c400-l.