Re: Programming style: using Classes or inline

On Thu, Mar 16, 2006 at 02:48:26PM +1100, Daniel Kasak wrote:
David wrote:

I first tried to keep my perl source separated into 3 files, all inline
code without making any packages, including the other two into the main
program by "use" statements,

For a little perspective, my code now occupies some 1500+ lines.

Once I got to that point ( ie things got very messy ), I split things up 
like this:

I can't say if my program has gotten to the point that it's "messy", but
I really think modularization is the way to go.  That was my original
intent, with the separate files, but got a bit hung up when "strict"
didn't allow globals.

[ ... file layout ... ]

Looks very logical.

If you're doing database stuff, you should check out my website:

I have visited your site.  It did seem interesting.  I'll go back and
look around some more.

I've automated a LOT of the mundane stuff required for dealing with 
databases. Everything is extremely well tested on MySQL ( and kinda 
tested with SQL Server ). I'd love to have some feedback from Postgres 
users ...

I'll give it a shot and see what I find.  I believe I've seen
announcements from you posted from you on the list.  In fact, I do
believe I'm keeping the latest one in my mailbox for reference.

as long as they don't start flaming me for using MySQL :)

I don't see why it should matter what one uses, as long as it suits
one's needs.

I've got Gtk2::Ex::DBI for dealing with 'normal' forms ( ie Access
forms ), and Gtk2::Ex::Datasheet::DBI for dealing with ... datasheet
... type things. I've also got PDF::ReportWriter for doing printable
reports. I'm on the verge of a 1.1 release of this, which will have
full XML report definition support :) Stay tuned for this 'real soon

It sounds interesting and useful.  Thanks for responding.

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]