Re: [pygame] constructor nomenclature

["ShredWheat" <shredwheat@mediaone.net>]

> I vote for having constructors with the same name as the type. As the
> types are capitalized, so should the constructors.

no need to wait around for the hand-recounts. i think this opinion is
shared by enough (myself also). the previously shnipped table has been
realized (aside from the joystick module).
 


> Maybe, but for me it's starting to be quite much work. I have so far ~75
> files and ~9kloc, so it's quite a lot to go through. Especially as my
> limited Python knowledge doesn't make it any easier to fix the changes
> than: fix, run, spot error, fix, run, spot error... ad nauseum
> 
> Is there some way to go through the code and find errors (like a compiler
> does)? Now there usually is some old code in some obscure function that
> does not get called every game, but when it does it again crashes with
> references to old code. This can be frustrating, especially if it was
> days/weeks since I made the changes.


sadly, i have to admit that after my first 'best effort' update 
for each of the examples eventually comes back to the method you
describe. fortunately for the pygame examples they are up and running
after 3-4 run/spot-error cycles. the examples total only a little over
1000 lines of code, and the largest is aliens.py at around 410 lines.

this is one of python's big drawbacks to everything being so dynamic.
it's impossible to detect all this stuff 100%. in any case it would be
really helpful if there was some tool that could at least give some
controllable degree of warnings.

sorry for the troubles there, jan. as soon as the interface gets
locked down, the happier we'll all be. as for now, i've mentioned
the next release will be held off until things calm down. you might
want to wait on updating until then? the only problem with that is it
stinks writing new code for something you know is already changed.


____________________________________
pygame mailing list
pygame-users@seul.org
http://pygame.seul.org