Pfiouh, thanks, I began to fear I had broken everything.
I just tested, indeed
a = [1, 2, 3]
for i in a[1:]:
translates to
$m['a'] = $p['list']([1, 2, 3]);
$iter1_iter = $p['__getslice']($m['a'], 1, null);
which looks fine.
Regards,
PKL
Le 09/02/2012 19:52, Lex Berezhny a écrit :
> Btw, this problem went away. It's possible I had some conflict of old
> and new javascript....
>
> I cannot replicate it.
>
> - lex
>
> On Thu, Feb 9, 2012 at 1:48 PM, Pascal Chambon<[email protected]> wrote:
>> Le 08/02/2012 17:58, Lex Berezhny a écrit :
>>> On Sun, Feb 5, 2012 at 12:39 PM, Pascal Chambon<[email protected]>
>>> wrote:
>>>> All tests are passing, except some added by Daniel (maybe his last
>>>> commit wasn't stable, or maybe I've broken stuffs while merging), so I
>>>> consider there is no regression.
>>>> I'll file bugreports later to "silence" these broken tests (mainly
>>>> dealing with sets and extended slices).
>>>> Anyway, I hope some people will check that /master can still compile
>>>> their current projects (I work on windows...)
>>> My project breaks on the following line after the upgrades:
>>>
>>> for tabValues in tabs[1:]:
>>>
>>> With the following error:
>>>
>>> Uncaught TypeError: Object slice([('tab', 'Tab')], 1, None) has no
>>> method '__iter__'
>>>
>> OMG it still there IS a regression...
>>
>> STop searching for bisects, that's just the merge with Daniel's work
>> which must be the cause of that. He introducted "slice" objects, that
>> were mainly meant to be used for assignment of extended slices, but
>> there seems to be a border effect here, your
>>
>> tabs[1:] gets turned into a slice object instead of just applying the
>> cutting (with __getslice() in translated code).
>>
>> It needs to be investigated directly.
>>
>> Regards,
>> PKL
