Beefy Boxes and Bandwidth Generously Provided by pair Networks
"be consistent"

Re: irritation makes perls

by CaMelRyder (Pilgrim)
on Sep 30, 2009 at 21:59 UTC ( #798469=note: print w/replies, xml ) Need Help??

in reply to irritation makes perls

I hate hate hate the negative logic constructs such as unless.
¥peace from CaMelRyder¥

Replies are listed 'Best First'.
Re^2: irritation makes perls
by Joost (Canon) on Sep 30, 2009 at 23:32 UTC
    You don't have to use them :)

    I hate that some stuff just ISN'T there:

    The OO system. It can do pretty much everything you want from a class based OO system, but it's too verbose to the point of discouraging good practices (i.e. no good, fast, standard, portable way doing private instance variables and methods sucks). There are good modules that help, but too late - they have tons of dependencies and most code you're working with won't use them. Class::MOP and related modules should have been in the core since 5.0 and perl's built-in collections should have been based upon the standard OO model.

    No *real* lisp-style macros. Personally, I think lisp macros are probably not workable in perl anyway, but once you've used them, they're absolutely amazing.

    No good inter-thread communication system. Why can't I pass real objects from one thread to another? IMO this makes threads in pure-perl code completely useless. You have to do all the work you have to do in forking code, and the forking code is probably more stable.

    Auto-vification has it's issues too, especially with strict/warnings enabled.

    Everything else, I've already mentioned before too many times. For instance: Re^3: Perl Vs Ruby and Re: No garbage collection for my-variables.

      Sure, I don't have to use them but that doesn't mean that I don't run into them while maintaining other people's code.
      ¥peace from CaMelRyder¥

Log In?

What's my password?
Create A New User
Node Status?
node history
Node Type: note [id://798469]
[dazz]: Hi I have grabbed an image from an IP camera with Image::Grab. I then want to pass that image object to a subroutine where I do a read-only test on the image with Image:Magick.
[dazz]: How do I pass an image object to a subroutine and then apply a Image::Magick a read-only method to the image object???
[dazz]: Also, I want to use Image::Magick to annotate and composite (not in a sub). How do I take a Image::Grab object and apply Image::Magick write methods to it??
[dazz]: At present, I am saving the Image::Grab image to disk, then creating a new Image::Magick object that reads the disk file.

How do I use this? | Other CB clients
Other Users?
Others pondering the Monastery: (6)
As of 2017-03-27 07:40 GMT
Find Nodes?
    Voting Booth?
    Should Pluto Get Its Planethood Back?

    Results (317 votes). Check out past polls.