Slash Boxes
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

use Perl Log In

Log In

[ Create a new account ]

vek (2312)

  (email not shown publicly)

Journal of vek (2312)

Tuesday May 14, 2002
05:23 PM


[ #4915 ]

So, how have I just spent my afternoon? Debugging a 646 line Javascript monstrosity from hell thats what. I fixed the problem but all I can say is - yuk. Unfortunately I don't have (a)the time (b)the patience or (c)the authority to re-write the fscker.

First PL/SQL, now Javascript - so when do I get to work on some Perl code again?


The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
More | Login | Reply
Loading... please wait.
  • Imho the problem with EcmaScript (and its JavaScript deviant variants) is not so much that it's a bad language -- it has limits and faults, but so do all the other ones -- but more that it's a language that was taken over by people that know nothing of programming (and that's not taking into account differing implementations if you're coding for the web at large).

    I've developed a rather large (several thousand lines) EcmaScript app for a thin-client (using SVG of course) with little prior EcmaScrip


    -- Robin Berjon []

  • javascript fun (Score:2, Informative)

    I seem to have been doing way too much Javascript recently. The main problem I've been finding is that the error messages are pretty useless, IE thinks everything wrong is an "object missing" and gives up random line numbers. Mozilla has been a life saver, the javascript console is fantastic. Another issue is when different files, the javascript interpreters seem to have issues with both scoping and reporting where on earth a problem is.

    The thing that really drove me mad is that some DHTML stuff wasn't er

    • Javascript console++

      I've also been playing with "venkman"[1] - their Javascript "debugger" for the past couple of days.

      [1] That's such a cool "blast-from-the-past" name, I used it for a cron account recently - the first words from my sysadmin: "isn't that the guy from Ghostbusters?"

  • I've been there. Hold on, brother.

    My latest bugaboo was a relatively insane bit of embedded SQL. It was intended to update a product's property. (I still don't know what that means or entails.) It checked to see if it was actually deleting the property, so it could insert NULL. It checked to see if it had to update a key, where it did something else special. It eventually updated either a long or a short character column.

    The tricky part is, it interpolated the property name and the new property va