{"id":44747,"date":"2019-04-22T03:01:03","date_gmt":"2019-04-21T17:01:03","guid":{"rendered":"http:\/\/www.rjmprogramming.com.au\/ITblog\/?p=44747"},"modified":"2019-04-21T18:31:18","modified_gmt":"2019-04-21T08:31:18","slug":"html-event-disrupters-primer-tutorial","status":"publish","type":"post","link":"https:\/\/www.rjmprogramming.com.au\/ITblog\/html-event-disrupters-primer-tutorial\/","title":{"rendered":"HTML Event Disrupters Primer Tutorial"},"content":{"rendered":"
\"HTML<\/a>

HTML Event Disrupters Primer Tutorial<\/p><\/div>\n

Computer Programming has grown up a lot since the earlier languages, my favourite being, for years, FORTRAN, where a GOTO statement would not always be frowned upon, as much as anything because lazy programmers (cough, cough) could justify their “GOTO” fetishes with “well, all the error handling is GOTO anyway … so … there … ngah!”.<\/p>\n

But has it grown up all that much? Think of all the “break” and “return” statement possibilities everywhere. The fact is, the optimists will start something off on the quite likely 99% success rate path of coding, and “break”\/”return”\/”GOTO” code for that other 1% of reality that still needs attention.<\/p>\n

HTML event driven programming has its disrupters. We try here not to use them, so much so that even though yours truly loves event driven programming, I’d never, to my recollection, used …<\/p>\n