Debugging silent script errors
  • DaveDave May 2011

    A Twitter user has been having some problems with silent errors, which are indeed a complete pain in the ass. My experience of silent errors has been only when running erroneous scripts via fl.runScript();

    I do want as part of the framework have some kind of functionality that tackles this somehow, and this is my first test.

    It's a function that attempts to eval the contents of the passed uri, then will print any error messages (instead of failing), then finally will run the uri directly using an undocumented method of FLfile to get the actual line number of the error (but this could be erroneous itself if a nested script relies on scoped variables that may already be disposed of).

    fl.tryScript = function(uri)
    // if the file exists, test it
    // grab the passed-in file contents
    var path = '"' + FLfile.uriToPlatformPath(uri) + '"';
    fl.trace('Testing: ' + path);
    var jsfl =;

    // attempt to eval the JSFL

    // if it fails, print the error, then run the file standalone
    fl.trace('Running: ' + path);
    var exec = fl.version.match(/\bMAC\b/i) ? 'exec ' + path : path;

    // Let the user know the file doesn't exist
    fl.trace('Error: uri not found: ' + uri);

    var uri = 'file:///C|/temp/jsfl/bad-file.jsfl'


    Comments welcome.

  • DaveDave July 2011

    This is now all built into xjsfl.file.load()

Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!

Sign In with OpenID Sign In with Google Sign In with Twitter

Sign In Apply for Membership