[Seaside-dev] apparent corruption in JQuery-Core-lr.110.mcz

Dale Henrichs dhenrich at vmware.com
Tue Nov 9 17:55:17 UTC 2010


Lukas,

Thanks!

Dale

On 11/08/2010 05:41 PM, Lukas Renggli wrote:
> Thank you Dale for reporting this problem. I will add a Code Critics
> rule for that and I fixed it in
>
>     Name: JQuery-Core-lr.111
>     Author: lr
>     Time: 8 November 2010, 10:40:01 pm
>     UUID: 08b2d589-1a62-4a1e-bc0a-347417ca8cc0
>     Ancestors: JQuery-Core-lr.110
>
>     - fixed the WideString method JQDevelopmentLibrary>>jQueryJs
>
> Lukas
>
> On 8 November 2010 20:33, Dale Henrichs<dhenrich at vmware.com>  wrote:
>> In a Pharo image, the source for JQDevelopmentLibrary>>jQueryJs (in
>> JQuery-Core-lr.110.mcz) has some non-ascii characters embedded in the method
>> source:
>>
>>                 return this[ optall.queue === false ? "each" : "queue"
>> ](function() {
>>                         // XXX ‘this’ does not always have a nodeName
>> when running the
>>                         // test suite
>>
>> ...this causes trouble when loading into GemStone as the sourceString is
>> corrupted... looking at the sourceString:
>>
>>   (JQDevelopmentLibrary sourceCodeAt: #jQueryJs) asString class
>>
>> I get back WideString when it should be ByteString. This is a "known
>> problem" that Monticello does not handle multi-byte strings in a platform
>> independent way...
>>
>> Dale
>> _______________________________________________
>> seaside-dev mailing list
>> seaside-dev at lists.squeakfoundation.org
>> http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev
>>
>
>
>


More information about the seaside-dev mailing list