We load AST-Core as part of Moose and it loads and works fine in PharoCore 12551.
Doru
On 4 Dec 2010, at 14:05, Guillermo Polito wrote:
> Maybe it is.
>
> I didn't have the last last last version because my image didn't want to update. Another issue for that :P.
> I used the last prebuild core.
>
> On Sat, Dec 4, 2010 at 9:55 AM, Benjamin <
[hidden email]> wrote:
> A fix has been integrated for that ...
> Strange :s
>
> Ben
>
>
>
> On Dec 4, 2010, at 1:49 PM, Stéphane Ducasse wrote:
>
> Excellent initiative!!!
>
> On Dec 4, 2010, at 9:12 AM, Guillermo Polito wrote:
>
> Hi!
>
> I was trying to load ConfigurationOfPharo in Core 1.2, so we can (slowly) get a Dev image. So It began well, but when it reached AST-Core-lr.84, it raised up an exception:
>
> "subscript is out of bounds: -1"
>
> It is mainly caused by CommentReference>>parseTimestampFrom:
>
> Which has the next comment:
>
> "Timestampstrings can be of the form:
> <authorname><date><time>.
> <authorname><date>
> <date><time>
> <date><time><authorname>
> <date><authorname>
> <historical>"
>
> The string timestamp is '<historical>' indeed, but it does the follow check:
>
> ^ (aString isEmpty or:[aString = 'historical'])
> ifTrue:[DateAndTime new]
> ifFalse:[ here comes the error ...
>
> Shouldn't that check be
>
> ^ (aString isEmpty or:[aString = '<historical>'])
>
> ??
>
> Cheers,
> Guille
>
>
>
>
>
--
www.tudorgirba.com
"One cannot do more than one can do."
Locked
