On Fri, August 29, 2014 19:41, Andrea Faulds wrote:
>
> On 29 Aug 2014, at 17:39, Anatol Belski wrote:
>
>
>> On Fri, August 29, 2014 17:54, Andrea Faulds wrote:
>>
>>
>>> I’d just leave things as they are… though I suppose there might be
>>> some benefit to switching to size_t for string offsets
On 29 Aug 2014, at 17:39, Anatol Belski wrote:
> On Fri, August 29, 2014 17:54, Andrea Faulds wrote:
>
>> I’d just leave things as they are… though I suppose there might be some
>> benefit to switching to size_t for string offsets. Does that avoid a cast
>> in the generated assembly?
> My point
On Fri, August 29, 2014 17:54, Andrea Faulds wrote:
>
> On 29 Aug 2014, at 16:49, Anatol Belski wrote:
>
>
>> Hi,
>>
>>
>> while refining the big string support, it turned out that we've an
> issue.
>> The syntax like $s[42] = 'x'; is currently inconsistend, because we
>> have uint32 for string o
On 29 Aug 2014, at 16:49, Anatol Belski wrote:
> Hi,
>
> while refining the big string support, it turned out that we've an issue.
> The syntax like $s[42] = 'x'; is currently inconsistend, because we have
> uint32 for string offsets. This actually means, the behaviour is currently
> only avail
Hi,
while refining the big string support, it turned out that we've an issue.
The syntax like $s[42] = 'x'; is currently inconsistend, because we have
uint32 for string offsets. This actually means, the behaviour is currently
only available in the old style and can handle not more than 2gb big
str
