In 1974, when memory and processing power was very expensive, programmers were busy doing a lot of poking and peeking and jumping to save memory and processor-time, and causing bugs because there was no safety protecting them against errors.
We have cars with the power of 300 horses or more. Do you need to understand horses to drive them? There is nothing you can learn from programmers from 1974. On 07-10-14 23:47, Colin Sutton wrote: > Whereas now we wait until the bugs appear? > > On 8 Oct 2014, at 8:33 am, Diego Bosc? <yampeku at gmail.com> wrote: > >> I assume that back then "premature optimization" was doing pest >> control before bugs appeared ;D >> >> 2014-10-07 23:27 GMT+02:00 Bert Verhees <bert.verhees at rosa.nl>: >>> On 07-10-14 22:57, Seref Arikan wrote: >>> >>> Knuth, Donald E. "Structured Programming with go to Statements." ACM >>> Computing Surveys (CSUR) 6.4 (1974): 261-301. >>> >>> Did you see the date? >>> >>> Programming has changed a bit since then >>> >>> _______________________________________________ >>> openEHR-technical mailing list >>> openEHR-technical at lists.openehr.org >>> http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org >> _______________________________________________ >> openEHR-technical mailing list >> openEHR-technical at lists.openehr.org >> http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org > ##################################################################################### > Scanned by MailMarshal - M86 Security's comprehensive email content security > solution. > ##################################################################################### > > ________________________________________ > IMPORTANT NOTICE: This e-mail and any attachment to it are intended only to > be read or used by the named addressee. It is confidential and may contain > legally privileged information. No confidentiality or privilege is waived or > lost by any mistaken transmission to you. The CTC is not responsible for any > unauthorised alterations to this e-mail or attachment to it. Views expressed > in this message are those of the individual sender, and are not necessarily > the views of the CTC. If you receive this e-mail in error, please immediately > delete it and notify the sender. You must not disclose, copy or use any part > of this e-mail if you are not the intended recipient. > ________________________________________ > > _______________________________________________ > openEHR-technical mailing list > openEHR-technical at lists.openehr.org > http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org
