Don might be able to diagnose why the original source filename and line number are getting discarded... as a workaround it may be possible to run the flex compiler from the command line on the .as intermediate files and see what it says.
First off, try running lzc from the command line, if you're not already, it might have some output that's getting stripped in the LPS server If that doesn't help then you can do lzc -ldebug your_app.lzx And it will print out a shell command it uses to run the flex compiler. If you cut and paste that into the shell, it will run flex, and output compiler errors to the console. You can then probably deduce which lzx source file the error came from, by looking in the .as file. It should have some comments in it pointing to the LZX source file and line (which were supposed to be mapped by our backend to give you the source locations, but must be getting swallowed someplace) On Fri, Jun 3, 2011 at 7:29 PM, Antun Karlovac <[email protected]>wrote: > Hi all, > > I get the following compilation warning when compiling an app. There's no > file name, but there is a line number. > > ----------------------- > Compilation Warnings > > <snip some other warnings> > Encountered " "," ", "" at line 114, column 88. > Was expecting one of: > <EOF> > ";" ... > ----------------------- > > Any idea of what to look for? > > I tried searching the source to see what shows up on line 114 of every > file, but there's just too many to sift through: > > find . -name '*.lzx' -exec sed -n '114{p;q;}' {} \; > > -Antun > -- Henry Minsky Nest Labs
