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.

Ahhhhh PHP you evil dog... 1 Comment More | Login | Reply /

 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • However I was lucky enough to be able to code the back end admin interface with perl/DBI,DBD::mysql/CGI.pm/CSS before having to diddle with the front end PHP/CSS/Javascript

    SO far it's all coming together rather well, but like someone else here said, if I have to write preg_match* or ereg_match* one more damn time, I swear to god I'm gonna kill -9 /dev/universe.

    *sigh* why the hell does it have to be so similar to perl? I'd be fine if it were widely different. and the slight differences are a major PITA.

    continue in php means next in perl.
    there is NO SUCH THING as a continue block.
    break in php means last in perl.

    crap like this.

    I hear php was originally based on perl, and if so why the crapulous miasma of hell did they have to change it so much?

    there's not even an 'unless' nor can I change the ordering of if statements

    I can't do

    blah($attr) unless $row->id == $whatever;
    or
    blah($attr) if !($row->id == $whatever);
    or even
    unless ($row->id == $whatever) { blah($attr);}

    I gotta do

    if ( !($row->id == $whatever) ) {
          blah($attr);
    }

    messy, very very messy. AND ugly as &*^#$^.

    shoot me now. you'd be doing me a favor.
Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.