code file in with syntax errors & undeclareds

This doesn't seem like it's working as it ought:-

filein some code with a syntax error, say due to the change from old code to Closures, where a temp var name from a block arg is later (mis)used as a method temp. You get a syntax error window, fix the problem with your Mighty Code Worrier skillz and continue.

filein some code that refers to a class not yet in the image, because, well that's what happens. You might notice the system telling you about Undeclared if you have a Transcript open.

Now filein some code with *both* problems. Oh, bother, said Pooh.

You can fix the syntax error all you like - but will the system be nice and deal with the undeclared this time? Will it buggery. It would be nice if it were nice.

tim
--
tim Rowledge; [hidden email]; http://www.rowledge.org/tim
Useful random insult:- Pedaling real fast, but not getting anywhere.

On 11 July 2013 22:46, tim Rowledge <[hidden email]> wrote:
> This doesn't seem like it's working as it ought:-
>
> filein some code with a syntax error, say due to the change from old code to Closures, where a temp var name from a block arg is later (mis)used as a method temp. You get a syntax error window, fix the problem with your Mighty Code Worrier skillz and continue.
>
> filein some code that refers to a class not yet in the image, because, well that's what happens. You might notice the system telling you about Undeclared if you have a Transcript open.
>
> Now filein some code with *both* problems. Oh, bother, said Pooh.
>
> You can fix the syntax error all you like - but will the system be nice and deal with the undeclared this time? Will it buggery. It would be nice if it were nice.

Of course this sad state of affairs needs recording in the form of a
bug report. But without me having actually tried to replicate the
problem, what happens?

frank

> tim
> --
> tim Rowledge; [hidden email]; http://www.rowledge.org/tim
> Useful random insult:- Pedaling real fast, but not getting anywhere.
>
>
>

On 19-07-2013, at 9:21 AM, Frank Shearar <[hidden email]> wrote:
>
> Of course this sad state of affairs needs recording in the form of a
> bug report. But without me having actually tried to replicate the
> problem, what happens?

What *appears* to happen is that a chunk with both undeclared names (typically a class that doesn't exist yet) and a syntax error will cause a SyntaxError notifier to pen and when you fix the syntax error and accept the edit all the handling of the undeclared names is ignored(? failed? skipped?).

I'll try to spend a few minutes making some tests and see if it is consistent.


tim
--
tim Rowledge; [hidden email]; http://www.rowledge.org/tim
"Bother!" said Pooh, as he pulled Piglet out the mincer.