On Mon, 25 Oct 1999, Axel Rose wrote: > I experience the number and names of folders within the "MacPerl Ÿ" folder > as very confusing. > > Why is there a "MacPerl Scripts" and a "macscripts" folder? > Why is there an "ext" folder with mostly .t files? Is this for > testing - then why isn't it named appropriately? This is the way programming environment distributions look, as a rule. It's not even that MacPerl is based on UNIX Perl, it's just that there is a lot of stuff. I sympathize to some degree, and I suppose the argument can be made that some rationalization of folder placements and names could occur. > What module is used when - ":lib:Mac:AppleEvents.pm" or "lib:MacPPC:Mac: > AppleEvents:AppleEvents"? > Well, in this kind of circumstance there is *no* confusion once you realize that binary modules have 2 parts - the .pm file which is located in the usual place, and the shared library which is located in the MacPPC or MacCFM68K folder in a library folder. > What do others think? > I consider the pure amount of folders and files in the top level folder > harder to grasp when the "README.???" problem so thoroughly discussed here. > It could be worse. Look at the Codewarrior distribution, or a TeX distribution like CMacTeX, and enjoy... :-) Arved # ===== Want to unsubscribe from this list? # ===== Send mail with body "unsubscribe" to macperl-request@macperl.org