Re^2: Upload a new application

To avoid the inevitable "Where's the POD?" bug reports, I suggest creating POD for your top module and your bin scripts (whatever you intend users to use)

The start script of my application sudokutrainer.pl contains a few lines of code and the general part of the doku, among this a brief description of the 3 main uses of the program together with the location of the regarding POD file. The other .pl file contains its own POD section. All 5 POD files are placed by Module::Build into a common subdir Trainer/pod, so it should be possible for the user to find all of them.

Comment on Re^2: Upload a new application

Replies are listed 'Best First'.
Re^3: Upload a new application by tobyink (Canon) on Dec 11, 2013 at 20:31 UTC
Generally speaking, you should try to avoid naming scripts intended for installation `foo.pl`. Just call it `foo`. `use Moops; class Cow :rw { has name => (default => 'Ermintrude') }; say Cow->new->name`	[reply] [d/l] [select]
Re^4: Upload a new application by GUIfriend (Sexton) on Dec 12, 2013 at 12:12 UTC
Is this your personal opinion, or did I miss a rule in the guidelines for uploading modules to PAUSE? Extensions are nice since they give a hint (to the computer and to the user) about the file type. I like clarity. That's my personal opinion. BTW, on Windows with ActivePerl the command Build install creates a batch script for each newly installed script. So the user has the choice between foo.pl, foo.bat, and foo to start foo.pl.	[reply]
Re^5: Upload a new application by tobyink (Canon) on Dec 12, 2013 at 17:16 UTC
There is certainly no rule, but it's a preference I've seen widely expressed, for example in the documentation for Module::Install. `use Moops; class Cow :rw { has name => (default => 'Ermintrude') }; say Cow->new->name`	[reply]