Rich Burridge wrote:
Dan Price wrote:
...
Also, I would recommend putting what is essentially "main" into a
function, and
calling that. This helps a lot with pylint because it reduces the
number of
variables which are at global scope.
I agree. And for somebody coming along and trying to learn the code,
it would be nice if all the "top level" code could be in one place
rather than
sprinkled in between the def functions and class sections (for example
line 279
and lines 803-839).
ok...
Will the files under 118/common be really under 121/common
when David does his resync?
Thanks.
They work on both and generate the right code; they basically clean
up some bugs where solaris.py was too permissive.
- Bart
--
Bart Smaalders Solaris Kernel Performance
[email protected] http://blogs.sun.com/barts
"You will contribute more with mercurial than with thunderbird."
_______________________________________________
pkg-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
