On 25.08.2010 03:02, Xiong Changnian wrote:
You may find the register in which I write overly formal. I don't wish
to insult anyone who may be more comfortable writing in another style. I
struggle to write clearly and accurately. I'm aware that my words here
are immutable and I cannot suffer poor grammar to represent myself.
there is a fine line between "formally correct" and "obnoxious to read",
and you crossed it :-)
an example:
> However, I ask you to notice (in the project I currently offer to
> criticism) I intend to assist authors, such as myself, with automated
> suggestions we can bring with us to the consultation. This will not
> usurp the role of those who guide but may lessen the fuzziness of
> requests for guidance.
this paragraph is 100% correct, but still I don't understand what you
are trying to say. ("bring with us to the consultation"? uh? and who are
"those who guide"?).
seriously Xiong, while I appreciate all the evident effort you put into
this, I totally share nadim's feelings. your last mails are becoming
more and more vaporous and formal and less and less substantiated.
coming to your question, my only advice is: waiting for the perfect name
(or the perfect specification from a customer, for what matters) before
coding is a sure receipt for never doing nothing.
go ahead, write some code, show people what you did, then *when* and
*if* it works, ask for naming advices before submitting to CPAN.
a name change on the run *must* take less time than doing any other
needed refactoring, otherwise you are doing it wrong.
> I also have underway a testing framework for which I have no good name.
> I'd appreciate any suggestions for naming it.
here, on the other hand, I'm pretty sure the proper name is
Test::MOAR::MOAR::MOAR :-)
cheers,
Aldo
