[Seaside-dev] Seaside 3.0a6ish

[Julian Fitzell]

I'm too exhausted to dig into this any further than reading it right now.
What Michael's talking about sounds fairly reasoned, but even assuming
everyone agrees, I think this is a disruptive change to throw in at this
point. What's the smallest change we can make to get it working "good
enough" for now?

My suggestion is that... no, crap, that doesn't work at all. I was going to
suggest we take the sprint at ESUG to focus on sorting out encoding/decoding
(I'd like to be a focus for 3.1 anyway). But since Philippe won't be there
and Lukas may or may not be, that's not really going to work out. :)

Ok, so I'm not sure when we tackle that, but the question is still what can
we do now that won't make us even *less* likely to release?

Julian

On Wed, May 19, 2010 at 7:31 PM, Michael Lucas-Smith <
mlucas-smith at cincom.com> wrote:

> On 5/19/10 11:07 AM, Michael Lucas-Smith wrote:
>
>> On 5/19/10 10:19 AM, Paolo Bonzini wrote:
>>
>>> On 05/19/2010 06:58 PM, Michael Lucas-Smith wrote:
>>>
>>>>
>>>> Can someone speak to the platforms that have trouble with #= here?
>>>>
>>>
>>> GNU Smalltalk has problems comparing an encoded string with
>>> #latin1String.
>>>
>> Perhaps we need to make the way we represent encoded bytes platform
> specific. If a platform chooses to represent bytes as characters in a
> string, so be it - but at least at the GRPlatform level we can draw a
> distinction between "A collection of bytes" and "a collection of characters"
> instead of always assuming the collection species is String?
>
>
> Michael
>
> _______________________________________________
> seaside-dev mailing list
> seaside-dev at lists.squeakfoundation.org
> http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.squeakfoundation.org/pipermail/seaside-dev/attachments/20100519/e482b5c7/attachment-0001.htm