[ale] Py[h]hon syntax (sic)

[Christopher Fowler]

On Fri, 2005-01-28 at 11:57, Joe Knapka wrote:

> But OO is definitely overkill in this example.
> 
The problem I have with Perl is that OOP is an afterthought when the
language was developed.  I'm looking at Pyhon to do pure OO
programming.  The reason to use objects in this program is that I will
eventually create a thread for each object.  That thread will be
responsible for that one device.  This eliminates the problem that round
robin introduces when trying to check a long list of devices to see if
they are up. 

If you start with device 1 and all are down it could be many minutes
before device 10 is even tested.  Not a good thing.  Every device needs
to be checked every 5 minutes, 60 minutes if by dial-up.  And there can
be no delays in testing because a few hosts ahead in line are down and
are slowing down each ping process.

> 
> >  This is one of my
> > biggest problems with Perl.
> 
> You worry about OTHER people reading and understanding your
> Perl code???

The code is part of a bigger system.  May perl programs, C, and Java
programs.  These are users that need not to read the code.  Plus with
the byte-code I can add code that validates the code is running on the
machine we sold the customer.
> 
> -- Joe