Re: Trying to name a file parsing module for CPAN

I do not mean to offend, but your module sounds like a solution in search of a problem. Why would someone else (who is not you), use this module instead of the other available modules using more standard formats, such as CSV, XML, etc?

After answering that only then would I consider uploading to CPAN, and then you would know more of how you should name it, knowing you know how others would/could use it.

I would not create a module that uses a non-standard file format when that format is significantly like other formats. For instance, we can give a nod to YAML, seeing it's substantially different from CSV (and has Data::Dumper like functionality built in), although this looks like an incompatible version of CSV that would only create confusion.

Thus, my opinion is... leave it off CPAN entirely until the use cases can be rationalized. And until you think your version is superior to other competing formats. The name should come more easily once you know what it is.

Comment on Re: Trying to name a file parsing module for CPAN

Replies are listed 'Best First'.
Re: Re: Trying to name a file parsing module for CPAN by fx (Pilgrim) on Jan 09, 2004 at 19:07 UTC
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.	[reply]

Replies are listed 'Best First'.

Re: Re: Trying to name a file parsing module for CPAN
by fx (Pilgrim) on Jan 09, 2004 at 19:07 UTC

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.

[reply]