Is "For preference I will wait until it has stopped feeping" clearer?
All it needs to do is take 3 sets of input rather than two. I've got a staroffice spreadsheet doing similar at home :-)
I don't know why perl modules all see the need to be so OOPy. But I might look at it in more detail if I decide I actually plan to use it. For now I'm happy enough with the web interface really.
I worked out the "feeping" reference about 2 minutes after I posted my comment when my brain woke up :)
I'm guessing that your spreadsheet has three columns for date, stone and lb ?
For day-to-day usage I'll carry on using the web interface. However for automated stuff like the "weekly weigh in" it made sense to automate the LJ posting :)
As for perl modules being OOPy.... it does make some sense as it means that you don't have to type lots of LJ::Simple::NewEntry(\%Event) or you don't have to worry about namespace pollution if you make NewEntry a part of the main namespace of your program.
The OOP system gets around part of this as whilst you have to do things like $lj = new LJ::Simple(...) you only have to refer to LJ::Simple once. After that it is just $lj->method() to call stuff within the object.
If I'm writing modules for inclusion in my own code which will not be used outside of that code I'll normally make them export their namespace so that I can use their functions directly.
However if I'm releasing the module it makes sense to avoid namespace collisions by using OOP stuff. Especially for things like this where you have a login which occurs once and then stuff done to that login value.
![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png)
timeasmymeasure
no subject
Date: 2002-08-20 08:42 am (UTC)All it needs to do is take 3 sets of input rather than two. I've got a staroffice spreadsheet doing similar at home :-)
I don't know why perl modules all see the need to be so OOPy. But I might look at it in more detail if I decide I actually plan to use it. For now I'm happy enough with the web interface really.
no subject
Date: 2002-08-20 08:52 am (UTC)I'm guessing that your spreadsheet has three columns for date, stone and lb ?
For day-to-day usage I'll carry on using the web interface. However for automated stuff like the "weekly weigh in" it made sense to automate the LJ posting :)
As for perl modules being OOPy.... it does make some sense as it means that you don't have to type lots of LJ::Simple::NewEntry(\%Event) or you don't have to worry about namespace pollution if you make NewEntry a part of the main namespace of your program.
The OOP system gets around part of this as whilst you have to do things like $lj = new LJ::Simple(...) you only have to refer to LJ::Simple once. After that it is just $lj->method() to call stuff within the object.
If I'm writing modules for inclusion in my own code which will not be used outside of that code I'll normally make them export their namespace so that I can use their functions directly.
However if I'm releasing the module it makes sense to avoid namespace collisions by using OOP stuff. Especially for things like this where you have a login which occurs once and then stuff done to that login value.