in reply to Pseudo-switch question

Why not just use Switch?

-- Randal L. Schwartz, Perl hacker
Be sure to read my standard disclaimer if this is a reply.

Replies are listed 'Best First'.
Re^2: Pseudo-switch question (bull)
by tye (Sage) on Jul 22, 2003 at 16:57 UTC

    Because...

    1. it can break correct, otherwise working code
    Well. I guess one reason is enough in this case.

    Update: I'd rather it were named Acme::Switch. It isn't really appropriate for use in production, IMO.

                    - tye
      Mind giving an example? I've never seen it break code, unless you try to break it on purpose. And just because a module is implemented a bit oddly dosen't mean it's a gag module.

        A quick search turned up Switch.pm gotchas? but there was also a thread just a couple of days ago where __DATA__ just doesn't work if you use Switch.

        I have no desire to use such so I don't keep up-to-date on exactly why I shouldn't.

        And just because a module is implemented a bit oddly dosen't mean it's a gag module.

        Thanks for guessing at what my reasons for thinking it should be renamed are. Sorry, wrong guess. Would you like to try again? Oh, wait! I already gave my reason. Imagine that.

                        - tye
Re: •Re: Pseudo-switch question
by fletcher_the_dog (Friar) on Jul 22, 2003 at 16:22 UTC
    I would but I can't guarentee that all the machines that will run my scripts will have perl 5.8 or the filter modules that "Switch" requires.