Beefy Boxes and Bandwidth Generously Provided by pair Networks
Come for the quick hacks, stay for the epiphanies.
 
PerlMonks  

Re: Re: Re: Method Calls on multiple objects

by tilly (Archbishop)
on Mar 27, 2004 at 08:03 UTC ( [id://340232]=note: print w/replies, xml ) Need Help??


in reply to Re: Re: Method Calls on multiple objects
in thread Method Calls on multiple objects

I'd agree with dragonchild. Yes, combining those styles is good. But strive to do it naturally, and you won't likely find the proposed method useful in many situations.

Remember, many small utilities that fit together in flexible ways. That's the ticket. :-)

  • Comment on Re: Re: Re: Method Calls on multiple objects

Replies are listed 'Best First'.
Re: Re: Re: Re: Method Calls on multiple objects
by flyingmoose (Priest) on Mar 27, 2004 at 19:32 UTC
    But strive to do it naturally, and you won't likely find the proposed method useful in many situations.

    I am not psychic here, what does 'more naturally' mean to you? Please elaborate and we can debate opinions on an equal front, but one saying 'what you do is not natural' is a assault on code without backing -- please explain your convictions and the merits of one style over another, and what is 'more or less natural' to you. You may find there are many of those who disagree, and as it stands, we don't even know what you mean. It's sort of like me saying "I am flyingmoose and your code is wrong because I am flyingmoose". That doesn't help folks, really it doesn't, and perhaps you need to look more carefully about what you are saying when you say it.

    Also, 'the proposed method' ... mine? Or Limbic~Regions. As I have been maintaining many times, I don't like Limbic's proposed method. I'm talking foreach, grep, and map! Seriously... are you arguing against foreach, grep, and map? Because it appears you have me confused with Limbic (as does dragonchild). Personally I think a simple use of non-combined map's or grep's is very natural, very readable, and obvious. I don't like dragonchild's particular re-coding of my Star Trek example -- I find that very unnatural, inflexible, and quite the maintaince problem.

      Well since "naturally" is an aesthetic judgement, it is hard to provide a precise definition. Rather you can provide contrasting examples and get a sense of someone else's tastes.

      But the reason for my comment is that Perl has enough ways to distribute actions over lists in a concise manner (map, foreach, etc, etc) that introducing a very specialized one doesn't meet the utility threshold to be worthwhile.

      But if you disagree, try to produce an example where such a method would make sense, and I'll produce an example that doesn't use the method, and we can compare. If it really is natural for your problem domain, then it shouldn't be hard to come up with a good example...

        We are already on the same page, it seems. But you and dragonchild still don't quite realize who you are arguing with. I was using map, and I never agreed that we needed a specialized tool -- I do not like Limbic's implementation (sorry, Limbic). Perhaps I misinterpreted your response based on the fact that I was the parent of your post...which was definitely confusing. I was saying "yes there is a need to sometimes call methods against a list", of which the whole thread got really convoluted rather quickly when I was trying to debate a percieved statement that "I can never see a reason to call a method on every object in a list", which didn't quite make sense.

        If Chewbacca lives on Endor, I say we forget about the whole sub-thread.

Log In?
Username:
Password:

What's my password?
Create A New User
Domain Nodelet?
Node Status?
node history
Node Type: note [id://340232]
help
Chatterbox?
and the web crawler heard nothing...

How do I use this?Last hourOther CB clients
Other Users?
Others scrutinizing the Monastery: (5)
As of 2024-04-16 05:26 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    No recent polls found