On Monday 18 September 2006 07:47, James Masters wrote: > I am rather amateur when it comes to OO methodology. If I don't use Loader > to define my table classes, then it appears that I have to create a whole > load of .pm files, one per table. Or if I do use Loader, then I have to > create a directory and an Extra.pm file for each table (for MySQL > relationships). My experience with performance is miminal but in my > travels, I have noticed that one of the worst things for it is opening and > reading files. However, I see that some documentation examples seem to > show multiple packages being defined within a single .pm module. This > might just be the way the documentation is written to avoid too much > clutter, though - not sure. Is it feasible to replace all those table .pm > files or the Extra.pm files with a single .pm file?
I'll let the "big boys" answer your questions above, but for the single .pm versus multiple, stick with multiple. Only those .pm files that you are using are opened and used, so the others don't hurt you. On the contrary, if you need only one package out of 50 but have to parse the whole file, that is probably a performance hit. Finally, naming and directory structure in perl are tightly coupled to make using the one-module/one-file methodology the standard. Sean ------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ Rose-db-object mailing list Rose-db-object@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/rose-db-object
