🚀 go-pugleaf

In article <25258@grebyn.com>, dougw@grebyn.com (Doug Worthington) writes:
|> 
|>		*** stuff deleted *** 
|> 
|>         My problem is this.  I want the user to get and set these
|> fields with the same routine names getValue and setValue without
|> having to cast the value as an char *, int etc.  When the user
|> includes the interface files with the program the compiler is confused
|> with the names complaining that there are more then one get/setValues.
|> Which there are, one for each type of field with a different
|> return/parameter type.  This lack of overloading is a bummer.  I
|> realize I am a bit braindead on this problem but why can't the
|> compiler do some scoping of the arguements and determine which method
|> to call.


The best (on also object oriented!) way to solve this problem is to use OBJECTS as
parameters of getValue() and setValue(). Having, a proper superclass, amy subclass
will fit...


Thomas Oeser


****** DISCLAIMER: All opinions stated here are strictly my own *********
-------------------------------------------------------------------------
Internet:	thomas%apgraph%ap542@ztivax.siemens.com
Europe:		thomas%apgraph%ap542@ztivax.UUCP
Phone:		+ 49 89 636 47537
Fax:		+ 49 89 636 45522
Postal Mail:	Siemens Nixdorf Information Systems AG, AP 153,
                Carl-Wery-Str. 22, D-8000 Munich 83, West Germany
-------------------------------------------------------------------------