All the Perl that's Practical to Extract and Report

Navigation

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
Without JavaScript enabled, you might want to
use the classic discussion system instead. If you login, you can remember this preference.

Please Log In to Continue

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

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.

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