two approaches to syntax checking

Authorware’s authorware script (aws) syntax checker will always be more new-coder friendly than any javascript checker could be. The fact that syntax checking occurs everytime you close an authorware script calc icon makes it so – the code in the calc icon is essentially being compiled. What’s great about this is that things like function calls and their arguments as well as object (icon) references can be verified without the need to execute the script. Once you close a calc you can be pretty much certain that your aws is syntactically correct. Of course it may not do what is expected of it but you are now free to test the behaviour of your guaranteed-to-compile piece. Certainly more javascript checking is possible, however due to the very nature of the language the modularized verification done at the icon level would be very difficult, if not impossible, to achieve. With augmentations like strict data typing and other features of the ECMAScript 4 standard this is partially achievable but the entire piece – not just a particluar calc – will always need to be compiled to implement the aws level of checking at the calc level.

Don’t read anything into this observation. Both solutions have their advantages and disadvantages.

Leave a Reply