>>Why use classes? Procedural code gets the job done, right?
>
>Classes are for when there's data that must travel with the code. No point using a class for a bunch of functions that don't share data.
>
>Tamar
And, in addition, methods live in the DataSession of there object, not in the one of the caller. This could have some surprise for example with SET commands.
Lutz
Words are given to man to enable him to conceal his true feelings.
Charles Maurice de Talleyrand-Périgord
Weeks of programming can save you hours of planning.
OffThere is no place like [::1]