I do not mean to offend
On the contrary, I welcome your feed back.

your module sounds like a solution in search of a problem
My module has solved a problem for me - in my case, at least, there was already a pre-existing problem ;)

Why would someone else ... use this module
...
I would not create a module that uses a non-standard file format
Part of my original question was whether the file format I am using has a name. If the style did have a name it would then make a release to CPAN more acceptable as, IMHO, it would mean enough people produce/use it to give it a name. If it had/has a name it would probably has uses and therefore others may benefit.

Thus, my opinion is... leave it off CPAN entirely until the use cases can be rationalized
I agree with you - there is no point in clogging up the CPAN directory with a pointless module that no-one will ever need, use or care about.

I did originally say that I wanted to release it to CPAN. The Perl community (this includes CPAN, Perlmonks and various Perl mailing lists) have done much to assist me over the years. I finally thought that I could give something back. It would appear that this occasion will have to wait until something more suitable comes along.

Many thanks.

In reply to Re: Re: Trying to name a file parsing module for CPAN by fx
in thread Trying to name a file parsing module for CPAN by fx

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.