QuadByteString at: error?

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

QuadByteString at: error?

SeanTAllen
Executing:

'jœ' at: 1

results in the following error:

The object ( string stuff here ) was neither of class String or DoubleByteString

Is this a known bug?
If yes, how does one get the characters from a QuadByteString?
Reply | Threaded
Open this post in threaded view
|

Re: QuadByteString at: error?

James Foster

On Feb 25, 2010, at 7:27 AM, Sean Allen wrote:

> Executing:
>
> 'jœ' at: 1
>
> results in the following error:
>
> The object ( string stuff here ) was neither of class String or DoubleByteString
>
> Is this a known bug?
> If yes, how does one get the characters from a QuadByteString?

Sean,

The problem is not with the #'at:' message, but with the attempt to compile the expression before executing it. According to the release notes for 2.3.0, "The compiler does not currently accept instances of QuadByteString. Attempting to compile a QuadByteString will generate an error."

You can generate a QuadByteString in other ways:

((QuadByteString
        with: (Character codePoint: 16r1000)
        with: (Character codePoint: 16r1001)
) at: 2) codePoint.


James
Reply | Threaded
Open this post in threaded view
|

Re: QuadByteString at: error?

SeanTAllen
On Thu, Feb 25, 2010 at 10:57 AM, James Foster
<[hidden email]> wrote:

>
> On Feb 25, 2010, at 7:27 AM, Sean Allen wrote:
>
>> Executing:
>>
>> 'jœ' at: 1
>>
>> results in the following error:
>>
>> The object ( string stuff here ) was neither of class String or DoubleByteString
>>
>> Is this a known bug?
>> If yes, how does one get the characters from a QuadByteString?
>
> Sean,
>
> The problem is not with the #'at:' message, but with the attempt to compile the expression before executing it. According to the release notes for 2.3.0, "The compiler does not currently accept instances of QuadByteString. Attempting to compile a QuadByteString will generate an error."
>

I've really only used 2.4 and haven't ever read the 2.3 release notes
so I missed that.