Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • As they say: "But it's just a Web language!"

    And that apparently serves as an excuse for any kind of demented design.

    • They also say "but it's easy to use".

      There's a lesson to be learned from PHP. I'm not sure what it is. It might just be how to market the external face of the technology to newbies (and managers). PHP proves that no amount of dementia will restrict the uptake of the technology, or the ability to attract/create core developers.

      Syntax aside, I'm stunned at PHP's popularity, especially when every little extension needs to be compiled into the engine ! Perhaps that's because there are only two extensio

      • by gnat (29) on 2002.02.28 13:13 (#5239) Journal
        That's not true--PHP supports dynamically loaded extensions.

        --Nat

        • Really? The few times I've set it up, there was a *long* list of extensions that could be compiled into PHP at build time. Maybe I'm confusing that with the large number of extensions that come with the standard distribution.

          Either case, that's good news (for next time I need to upgrade a client's PHP install).

          • Yeah, the normal approach taken is to satisfy as many people as possible. That involves linking in a shitload of things so the user never has to fiddle with their php.ini file (to preload via configuration) or call the dynaloader.

            --Nat

            • Um, Perl doesn't have a perl.ini file, and doesn't force users to call the dynaloader. Come to think of it, neither does Python. :-)

              It would be an interesting study to see how user-friendly the PHP model is vs. the other way to do it. Apache seems to have inherited a config file and used it exceedingly well - modules may be compiled in or dynamically loaded, but it's really not a huge concern. (It's compiling and installing modules post-install that needs work...)

              I keep trying to find areas where Per

              • Well I can tell you a few things.

                a) php is lightweight, this is why I (ab)use it.

                b) the function names suck (array_*?!)

                c) to me it makes a good case against Highlander variables

                Just yesterday I really found myself wanting to write
                (explode('?', $REQUEST_URI))[0])
                and ended up with
                array_shift(explode('?', $REQUEST_URI)))
                which isn't *too* bad I suppose.
                --
                Were that I say, pancakes?