The ERROR: line shown in my example below is correct, of course, but do we have to get all those Java messages too? It looked catastrophic, but in fact I was able to continue the Dbrowser session. (I inserted a line break in the ERROR: message because otherwise it got truncated in this copy.)
Hugh
'abc ;
ERROR: ca.mb.armchair.rel3.languages.tutoriald.parser.TokenMgrError: Lexical error at line 1, column 7.
Encountered: <EOF> after : "\'abc ;"
ca.mb.armchair.rel3.languages.tutoriald.parser.TokenMgrError: Lexical error at line 1, column 7. Encountered: <EOF> after : "\'abc ;" at ca.mb.armchair.rel3.languages.tutoriald.parser.TutorialDTokenManager.getNextToken(TutorialDTokenManager.java:2997) at ca.mb.armchair.rel3.languages.tutoriald.parser.TutorialD.getToken(TutorialD.java:10274) at ca.mb.armchair.rel3.languages.tutoriald.parser.TutorialD.jjtreeOpenNodeScope(TutorialD.java:6) at ca.mb.armchair.rel3.languages.tutoriald.parser.TutorialD.code(TutorialD.java:78) at ca.mb.armchair.rel3.interpreter.Interpreter.interpret(Interpreter.java:165) at ca.mb.armchair.rel3.interpreter.Interpreter.interpret(Interpreter.java:181) at ca.mb.armchair.rel3.interpreter.Interpreter.interpret(Interpreter.java:185) at ca.mb.armchair.rel3.client.stream.ClientLocalConnection.sendExecute(ClientLocalConnection.java:60) at ca.mb.armchair.rel3.client.string.ClientLocal.sendExecute(ClientLocal.java:56) at ca.mb.armchair.rel3.dbrowser.ui.PanelCommandline$34.doInBackground(PanelCommandline.java:1066) at javax.swing.SwingWorker$1.call(Unknown Source) at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source) at java.util.concurrent.FutureTask.run(Unknown Source) at javax.swing.SwingWorker.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source)
Missing quote gives rise to slew of messages
-
- Posts: 124
- Joined: Sat May 24, 2008 4:49 pm
Re: Missing quote gives rise to slew of messages
This will be fixed in the next update.