Thanks a lot to all of you !
I am really just starting to 'learn becoming an "efficient" programmer' (i have started almost from scratch), and your help is very appreciated.

Your messages made me realize a bit more that each person and project can/should have a workflow that suits it.
It can be the same as other persons/project, for the sake of compatibility or easier communication. Or it can be personal and unique for the sake of efficiency, if there is no need for communication and work protocols.

I work alone on my code (it might change some day - who knows), so i understand BrowserUk's efficiency motivations. And i would like to be able to work with others some day, so i want to try and learn a bit of Revision Control and "Test::* testing" for example.

In your messages i have learned many things :

- That i don't need to create 5 different Module::Starter directories for my 5 modules, and that makes quite a big difference in terms "lib" thingies.

- That i could use 

perl -I

[download]
I didn't know about it, thank you. Are PERL5LIB and lib not easier to use? To me, the 3 of them seem to do exactly the same : give the information of "where are these sources that i need". PERL5LIB does it through an environment variable, lib does it in each source file, and -I does it on the command line. Any other difference?

- An alternative idea for having "non-boolean tests" directly in the source. What i don't like about it, is that it makes the source less readable : it becomes harder to search the interesting parts of the code.
But i like that it is run each time i run my code, and that i can be more creative than "ok". But...i like "ok" because it is easy to share : everybody understands what it means, when it appears on the screen.

- A clear tutorial on Revision Control

- Easier ways to manage my tests and run them, and a text about Regression Testing that i will most probably read.

... and a nice story !

Now i know how i want to start developing my own modules. Until now i felt lost in the profusion of tools and techniques, and by tiny details which make big differences (my 5 Module::Starter directories where a real pain).

Thank you, you're all great!

In reply to Re^2: Developing a module, how do you do it ? by mascip
in thread Developing a module, how do you do it ? by mascip

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.