Hi there, Zhang! I think what Brian meant is that we should get rid off all warnings now so we can find warnings that may be of concern easier.
Also, I keep nagging :) but I'd really like to see name changes of the types to follow the PEP. I also found a spelling error on line 152 in rev 1390 which generates a compile error. It's much easier if the code is warning free and PEP-correct even though the interface and implementations aren't complete, it will be better for testing as-is and you won't have the tedious task of correcting hundreds of occurences later. /Peter On 2008-06-23 (Mon) 13:49, 帆 张 wrote: > Hi, > > Thank you for your attention. In fact, these warnings are because of > forward types' declarations. When I compile these codes with my VC solution, > there are no such warnings, However, with GCC compiler, These warnings tell > us such types may be not defined yet. So, the warnings won't cause errors and > troubles. > > Best wishes > Zhang Fan > > > > Brian Fisher <[EMAIL PROTECTED]> 写道： > On Sun, Jun 22, 2008 at 4:21 AM, Peter Gebauer <[EMAIL PROTECTED]> wrote: > Yeah, SVN tried merging with the sources I changed, that was the prob. But > I'm definately getting warnings. > > > > Yeah, everybody gets the warnings - they were looked over to check for > obvious errors, and are now mostly casting and unused variables. It would be > nice for them to be gone so that if new warnings crop up the new ones get > more attention in case they represent a real error > > > > --------------------------------- > 雅虎邮箱，您的终生邮箱！
