in fact nothing is unlogical ... it's the gambas way... in gambas an error, impossibility, return true... in all the function that return a boolean
you can imagine to write this in that way CONST bError as Boolean =True if .MoveChild = bError then ... its the same ! in another way it limit the use of the NOT Function keyword exemple : if .MoveChild then .MoveBack if .MoveNext .MoveBack if .MoveParent then .MoveNext endif endif Endif 2009/4/29 Rolf-Werner Eilert <eilert-sprac...@t-online.de>: > Just one question for understanding it better: > > Why is e. g. MoveNext or MoveChild TRUE in case there is NOTHING and not > vice-versa? Seems pretty unlogical and looks somewhat strange in code... > > Regards > > Rolf > > ------------------------------------------------------------------------------ > Register Now & Save for Velocity, the Web Performance & Operations > Conference from O'Reilly Media. Velocity features a full day of > expert-led, hands-on workshops and two days of sessions from industry > leaders in dedicated Performance & Operations tracks. Use code vel09scf > and Save an extra 15% before 5/3. http://p.sf.net/sfu/velocityconf > _______________________________________________ > Gambas-user mailing list > Gambas-user@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/gambas-user > ------------------------------------------------------------------------------ Register Now & Save for Velocity, the Web Performance & Operations Conference from O'Reilly Media. Velocity features a full day of expert-led, hands-on workshops and two days of sessions from industry leaders in dedicated Performance & Operations tracks. Use code vel09scf and Save an extra 15% before 5/3. http://p.sf.net/sfu/velocityconf _______________________________________________ Gambas-user mailing list Gambas-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/gambas-user