Re: what's a callback?

From: Frank Bemelman (f.bemelmanq_at_xs4all.invalid.nl)
Date: 12/22/04 

Date: Wed, 22 Dec 2004 09:59:35 +0100

"John Larkin" <john@spamless.usa> schreef in bericht
news:cl1is0558091ki5r5k24093gtdqrcf5fls@4ax.com...
>
> OK, imagine trying to understand and maintain 100 millions lines of
> code like this. If you passed it through triple-DES encryption, it
> couldn't look much worse.

Well, you write, test, approve and forget ;) Most of the code is
pretty harmless and straight forward anyway.

There's a lot of things behind the scenes. Nobody is amazed when
he/she hits the print button and a printer dialog pops up. And I
have no idea how *your* printer dialog looks like. And neither
has a windows application, when it happens. And the printer driver
has no idea where your printer is, at lpt1, com2, usb or somewhere
on your ethernet network. And of course you expect a gentle warning
that it might be turned off, or has run out of paper or ink.
And you want to run it from 7 applications at the same time, each
using different papersizes, while your secretary wants the same
printer to print a *** of labels that she has put in the manual
feed tray...

That is just one example. It is a lot easier to write robust code
for a full featured pinball machine. 

-- 
Thanks, Frank.
(remove 'q' and 'invalid' when replying by email)
Loading