Topic: &class::method() != &func()


Author: rpost@cellar.org (hamilton)
Date: 10 Mar 92 08:01:57 GMT
Raw View
In attempting to create an object that envelopes hardware I've run into an
old problem.  In TC++ (at least) there is a difference between the address
of an object versus the address of a (standard C) function.  If anyone knows
if this is a problem with DOS or Borland then it is not an issue (I'll just
design a kludge that works and wait until I have a real system to work on).

But if this is a panplatform problem I would like to hear any suggestions.
At first I thought I was making a mistake trying to force an object to
encapsulate a piece of hardware.  But upon review some journals, especially
those by Parnas, it seems I should be making objects whose private methods
interact with hardware.

See you in Pittsburgh...