This is an extremely frustrating issue. It's still not clear to me why this
has to be the case. I can't think of a reason (other than convenience,
laziness, or poor initial design) why globals should have to be used for
vtable pointers.
The three issues suggested below are all completely unacceptable.
RE:
1. this is akin to rejecting the OO approach (because without inheritance,
languages are merely object-based, not object-oriented)
2. this is akin to saying that you don't need language support to do OO
programming. I fully agree, from a theoretical point of view. There's no
reason why you can't write OO programs in BASIC or Cobol. There is,
however, a reason why people *don't*.
3. this defeats the whole point of the launch code mechanism.
This thing has driven me very near to craziness in the last few months.
>Hi
> I was wondering if people who are coding their Palm apps in C++,
>tend to use virtual functions (and how) or tend to shy away from them
>due to their use of Global data.
>
>In 'Palm Database Programming' Eric Giguere suggests either
>1) avoid them
>2) simulate them
>3) relaunch app ( not supported by palm) if Global variables are not
>available e.g. find function
>
>
>Declan O'Reilly
