* On Wed, Jul 02 2008, Aristotle Pagaltzis wrote:
On this, I disagree.
Here’s litmus test: would you ever use the opposite adjective in
a description? If not, it’s not useful. I think you’ll agree that
no one would call a module Exception::Complicated except as a
joke. That means “easy”
* Jonathan Rockway [EMAIL PROTECTED] [2008-07-03 19:35]:
Of course, you lose a lot of power with that API. Tradeoffs.
Which is, as I said, what you want to communicate.
So I don't feel like I'm alone in coming up with weird-ass
names for things :)
That was tongue-in-cheek anyway, hence the
* Jonathan Rockway [EMAIL PROTECTED] [2008-07-02 18:30]:
* On Tue, Jul 01 2008, Aristotle Pagaltzis wrote:
If I see a module called Exception::Easy in a list of modules,
I have *absolutely no idea* what it does. In contrast, if it
was Exception::Class::Functions, I could immediately guess
* Aristotle Pagaltzis [EMAIL PROTECTED] [2008-07-03 00:25]:
In fact, the “simplified” in “simplified interface” is largely
redundant. Using an interface by definition means you are
looking for simplification in doing or accessing the thing that
the interface provides.
Similar words that say
# from Aristotle Pagaltzis
# on Wednesday 02 July 2008 15:21:
no one would call a module Exception::Complicated except as a
joke.
Well, you're going to have a hard time predicting what a gaggle of zany
programmers might do, especially if you dare them like that ;-)
I, for one, am seriously
* Eric Wilhelm [EMAIL PROTECTED] [2008-07-03 02:00]:
# from Aristotle Pagaltzis
# on Wednesday 02 July 2008 15:21:
no one would call a module Exception::Complicated except as a
joke.
Well, you're going to have a hard time predicting what a gaggle
of zany programmers might do, especially
On Wed, Jul 2, 2008 at 5:44 PM, Aristotle Pagaltzis [EMAIL PROTECTED] wrote:
* Aristotle Pagaltzis [EMAIL PROTECTED] [2008-07-03 00:25]:
No one would say that they are
trying to achieve slowness or inflexibility.
Drafted any mission-critical change control policies recently?
* sawyer x [EMAIL PROTECTED] [2008-07-01 08:10]:
personally I find ::Easy and ::Simple no more useful than
::Foo. It says absolutely nothing about what kind of ease or
simplicity I can expect, and CPAN has plenty of examples of
such modules exhibiting all possible interpretations of these
Hello Aristotle,
thanks for your feedback.
On Sun, Jun 29, 2008, Aristotle Pagaltzis wrote:
* Lutz Gehlen [EMAIL PROTECTED] [2008-06-28 13:55]:
The module uses the package Exception::Class::EasyThrow
but I don't know if this is really a good name.
It seems fairly reasonable to me. Putting
# from Lutz Gehlen
# on Monday 30 June 2008 11:43:
If the only call needed is mk_exception_functions(), that could
just be import().
Well, the reason against that is the mk_exception_methods function I
just mentionend. But I had not thought of using import,
Yes, even in the case of creating
Hi Lutz,
* Lutz Gehlen [EMAIL PROTECTED] [2008-06-30 20:30]:
The last reply of sawyer x convinced me that the Easy
extension is maybe not so bad.
personally I find ::Easy and ::Simple no more useful than ::Foo.
It says absolutely nothing about what kind of ease or simplicity
I can expect, and
Hi sawyer x,
thanks for your suggestion.
On Sun, Jun 29, 2008, sawyer x wrote:
How about Exception::Easy ?
The idea to put it out of the Exception::Class name space is
definitely worth considering because my module can in fact deal
with any class that implements a throw method and I am
I've personally noticed that a lot of modules use an Easy subspace to
show it's an interface or ability that's stripped down and made simple
for you. I think this would be your emphasis. That you haven't written
a new framework, but present an easy way to use the existing ones.
For example:
* Lutz Gehlen [EMAIL PROTECTED] [2008-06-28 13:55]:
The module uses the package Exception::Class::EasyThrow
but I don't know if this is really a good name.
It seems fairly reasonable to me. Putting it inside the
Exception::Class:: namespace seems better than not; but
once you accept that, the
# from Lutz Gehlen
# on Saturday 28 June 2008 04:51:
__PACKAGE__-mk_exception_functions
(messages = {foo = 'Error foo occurred.'},
exception_class = 'Exception::Class::Mine');
and later just call
foo() if($foo);
This requires you to inherit from the exception class, but it installs
Hello everybody,
I am developing a module to make throwing Exception::Class objects
easier. The goal is to make the code to throw an exception shorter
and to make it possible to keep all error messages at some central
place.
The module works quite similarly to Class::Accessor and provides a
16 matches
Mail list logo
