> That's useful information... most of my motivation for iterChildren()
> was to be consistent with other python methods like iteritems(),
> iterkeys(), etc., so if that's going away then I'm less motivated to
> stick with it. I haven't played with python3 so I didn't know that.
> See, I told you
That's useful information... most of my motivation for iterChildren()
was to be consistent with other python methods like iteritems(),
iterkeys(), etc., so if that's going away then I'm less motivated to
stick with it. I haven't played with python3 so I didn't know that.
See, I told you that you w
By the way, I don't hate iterChildren(). I just agree with the python
guys who don't feel that the word iter is necessary. (In python3,
iteritems doesn't exist anymore, it's just called items).
Nate
On Fri, Jul 30, 2010 at 10:45 PM, nathan binkert wrote:
>> I tried unproxying without sorting
> I tried unproxying without sorting and the regressions passed, so it looks
> like you were right that it's unnecessary. I then got rid of
> iterSortedChildren() and replaced the one remaining use with
> for obj in sorted(root.iterChildren(), key=lambda o: o.path()):
> obj.print_ini(ini_f
---
This is an automatically generated e-mail. To reply, visit:
http://reviews.m5sim.org/r/27/#review132
---
I tried unproxying without sorting and the regressions passed, so it looks
---
This is an automatically generated e-mail. To reply, visit:
http://reviews.m5sim.org/r/73/#review131
---
You need a space after "for" and "if" (see
http://m5sim.org/wiki/index.php
* build/ALPHA_SE/tests/fast/quick/00.hello/alpha/linux/inorder-timing
passed.
* build/ALPHA_SE/tests/fast/quick/00.hello/alpha/linux/simple-atomic passed.
* build/ALPHA_SE/tests/fast/quick/00.hello/alpha/linux/simple-timing-ruby
passed.
* build/ALPHA_SE/tests/fast/quick/00.hello/a
