On Thu, Mar 13, 2003 at 02:20:01PM +0200, Tuomo Valkonen wrote:
On Thu, Mar 13, 2003 at 01:50:13AM +0100, Andreas Happe wrote:
things i would pick from c++:
  * ...
  * assertions

Do you mean exceptions?

i understand under a assertion something in the way of an ASSERT(expression); which terminates the programm, if the exception is false and debug mode is activated. It should print out a detailed error message, including line#, exception, blah... and could be done as a #define. assertions can be enabled or disabled on demand (well I thing in C they have to be en/disabled on compile time, in Java this can be done at "runtime") and compile away into nothingless if not wanted.

massive usage of them should make debugging ion-devel easier.

exceptions are IMO not the way (TM) for ion. See threads on lkml on
threads in the linux kernel and why they are not used. I think the same
reasoning can be applied on a window manager.

RTTI is also a necessity -- just grep the Ion source for WTHING_IS and
WOBJ_IS.

how large is the performance impact of using RTTI with gcc?


Tuomo

Andreas
--
"Red Hat 5.2 puts all the commercial stuff on a seperate CD so you
know clearly what is what, and you can stick that CD in your
microwave and watch the pretty lights if you wish." -- Alan Cox

Reply via email to