Recent Nebraska updates are naughty

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
5 messages Options
Reply | Threaded
Open this post in threaded view
|

Recent Nebraska updates are naughty

timrowledge
While updating a fresh 16548 image I had to enable both  assigning to block arguments and underline assignment chars. I thougt we were trying to be nice and not do that?

tim
--
tim Rowledge; [hidden email]; http://www.rowledge.org/tim
It is easier to change the specification to fit the program than vice versa.



Reply | Threaded
Open this post in threaded view
|

Re: Recent Nebraska updates are naughty

timrowledge

> On 27-11-2017, at 10:24 AM, tim Rowledge <[hidden email]> wrote:
>
> While updating a fresh 16548 image I had to enable both  assigning to block arguments and underline assignment chars. I thougt we were trying to be nice and not do that?

OK, so the first weirdness is why the image was all the way back at 16548 when I have much more recent ones… oh, because I downloaded the ‘latest’ one off squeak.org and assumed the top item in the list was most recent. Sigh.

The point about block argument assigning and _ stands, though.


tim
--
tim Rowledge; [hidden email]; http://www.rowledge.org/tim
Strange OpCodes: RCR: Rewind Card Reader



Reply | Threaded
Open this post in threaded view
|

Re: Recent Nebraska updates are naughty

David T. Lewis
In reply to this post by timrowledge
Did I trigger that in Nebraska-dtl.51? If so it must be some existing
ancient code in that package that may still be in need of a clean up.

I see that you fixed one underscore assignment in August, perhaps there
are some more? The FixUnderscores utility, or Levente's improved version
thereof, would be the thing to use. I'm not sure how to find the
assignments to block arguments.

Dave


> While updating a fresh 16548 image I had to enable both  assigning to
> block arguments and underline assignment chars. I thougt we were trying to
> be nice and not do that?
>
> tim
> --
> tim Rowledge; [hidden email]; http://www.rowledge.org/tim
> It is easier to change the specification to fit the program than vice
> versa.
>
>
>
>



Reply | Threaded
Open this post in threaded view
|

Re: Recent Nebraska updates are naughty

timrowledge

> On 27-11-2017, at 11:59 AM, David T. Lewis <[hidden email]> wrote:
>
> Did I trigger that in Nebraska-dtl.51? If so it must be some existing
> ancient code in that package that may still be in need of a clean up.

Nebraska seems a likely place for quite a lot of _ usage since it is quite old.

>
> I see that you fixed one underscore assignment in August, perhaps there
> are some more? The FixUnderscores utility, or Levente's improved version
> thereof, would be the thing to use. I'm not sure how to find the
> assignments to block arguments.

Logically one ought to be able to look at all the methods and find out but it’s beyond my capability at this time of a Monday. (Crosses fingers, hopes somebody solves it before Tuesday and I have to admit not having a clue)


tim
--
tim Rowledge; [hidden email]; http://www.rowledge.org/tim
Useful random insult:- A room temperature IQ.



Reply | Threaded
Open this post in threaded view
|

Re: Recent Nebraska updates are naughty

David T. Lewis
On Mon, Nov 27, 2017 at 03:35:12PM -0800, tim Rowledge wrote:
>
> > On 27-11-2017, at 11:59 AM, David T. Lewis <[hidden email]> wrote:
> >
> > Did I trigger that in Nebraska-dtl.51? If so it must be some existing
> > ancient code in that package that may still be in need of a clean up.
>
> Nebraska seems a likely place for quite a lot of _ usage since it is quite old.

I loaded FixUnderscores from SqueakMap, then did FixUnderscores fixPackage: 'Nebraska'.
It did not seem to update anything, so I expect that there are no underscore
assignment characters remaining in package 'Nebraska'.

Dave