I've just tested what happens to a source with invalid syntax:
- from a File Browser fileIn action, correcting and accepting source in the
SyntaxError pop up let the fileIn continue
- from a MC load action, it won't work because some MethodAddition
compiledMethod isNil...


2013/9/13 H. Hirzel <hannes.hirzel at gmail.com>

> +1
> Any ideas how to implement these suggestions/hints?
>
> for example a hint about the
>
>      underscore assignment?
>
> H.
>
>
> On 9/13/13, Bert Freudenberg <bert at freudenbergs.de> wrote:
> > On 2013-09-13, at 10:20, Tobias Pape <Das.Linux at gmx.de> wrote:
> >
> >> Hi
> >>
> >> Am 13.09.2013 um 10:11 schrieb Bert Freudenberg <bert at freudenbergs.de>:
> >>
> >>> In particular if the syntax error notifier lets us easily fix an
> >>> occurrence when trying to load older code - does it?
> >>
> >> Personally, I really hate it when those syntax error windows pop up.
> >> I have to abort the whole loading, fix the code by hand and try again,
> >> don't I?
> >>  Your comment seems to imply that I can change the respective code and
> >> save it?
> >> If so, we _really_ should make that syntax error stuff more accessible.
> >> And probably indicate what preferences to tune to make certain code
> load.
> >> I mean, Squeak hasn't enabled underscore selectors by default, which
> >> I tripped over several times, with said syntax error window. Would be
> >> gorgeous if the window _could_ indicate which preference to tune…
> >>
> >>
> >> Best
> >>      -Tobias
> >
> > +1
> >
> > - Bert -
> >
> >
> >
> >
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.squeakfoundation.org/pipermail/squeak-dev/attachments/20130916/3bff3c81/attachment.htm