in reply to Module Organization

That’s purely up to you, isn”t it?   It’s your program ...

A modular topology can be pursued, for instance, “so that common code, behavior, or characteristics are commonized,” or they can simply represent a taxonomy -- the way that you naturally prefer to organize things and to think about them.   There are “suggestions” that one might make on this subject ... and of course, textbooks to be sold at high prices to unwilling students   ;-)   ... but, really, no hard-and-fast rules or ten commandments.   Whatever you decide, it will be something that you will be living with for quite some time, so ponder carefully.

Replies are listed 'Best First'.
Re^2: Module Organization
by Dwood (Acolyte) on Oct 13, 2010 at 20:08 UTC
    textbooks to be sold at high prices to unwilling students

    Hah! That actually reminded me that the head of our school's CS department had an O'Reilly Perl book he offered to give to me since it was just sitting on his shelf doing nothing...

    That’s purely up to you, isn”t it? It’s your program ...

    The thing that I probably left out was that I'm new to perl modules and CPAN... As well as how very oddly perl handles the concepts of objects and scalar variables, stuff like the perlboot tutorial: (just takes getting used to I guess)
    1. $a = "Class"; 2. $a->method(@args);

    Really put me up side down!

    I think I'm going to get tired of defining a new class every single time I wanted to add a new character... but I guess it wouldn't be a bad idea to start out with that.