On maandag, augustus 12, 2002, at 10:18 , Jack Jansen wrote: > > I already fear that I have to come up with some sort of a fix > for the range-check warning (more than 6000 lines worth of > constant definitions that can currently be copied verbatim from > C header files to Python will have to be parsed, and computed, > and all these things can contain references to other constants, > strings and who knows what more, see Mac/Lib/Carbon/*.py), I > really could do without more work on my plate... I'll retract this statement after a bit of research: it turns out there are only very few of those 6000 constants that actually run afoul of the warning, so I can fix those by hand. That is, if there's actually a warning for every bad constant, not just once per module... -- - Jack Jansen <Jack.Jansen@oratrix.com> http://www.cwi.nl/~jack - - If I can't dance I don't want to be part of your revolution -- Emma Goldman -
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4