Environment-caused SyntaxError running build scripts (was Re:
[squeak-dev] error when updating Squeak4.4-12327 to trunk)
Bert Freudenberg
bert at freudenbergs.de
Mon Mar 11 23:13:40 UTC 2013
On 2013-03-12, at 00:11, Frank Shearar <frank.shearar at gmail.com> wrote:
> It is Environments, and it's _after_ the image is updated: first the
> CI job runs update-image.st, copies this updated artifact, and in the
> copy runs prepare-test-image.st. That then fails because of a
> SyntaxError being thrown, saying this:
>
> DoIt
> Smalltalk
> at: #Log
> put: [:t1 |
> | t2 |
> t2 := #Invalid literal character ->#DateAndTime value now
> printString , ': ' , t1.
> FileStream stdout nextPutAll: t2;
> nextPut: Character lf;
> flush.
> ##Transcript value cr; show: t2].
>
> Compare that to the original source, from prepare-test-image.st in the CI job:
>
> Smalltalk at: #Log put: [:msg | | str |
> str := DateAndTime now printString, ': ', msg.
> FileStream stdout nextPutAll: str; nextPut: Character lf; flush.
> Transcript cr; show: str].
>
> Note the ## marks prepended to (some of) the class names. Colin? Thoughts?
I've seen that too. It happens I think when code gets decompiled.
- Bert -
More information about the Squeak-dev
mailing list
|