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 [hidden email] http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev |
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 <[hidden email]> 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 > [hidden email] > http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev > -- Lukas Renggli www.lukas-renggli.ch _______________________________________________ seaside-dev mailing list [hidden email] http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev |
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<[hidden email]> 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 >> [hidden email] >> http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev >> > > > seaside-dev mailing list [hidden email] http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev |
Free forum by Nabble | Edit this page |