| Technique for "method_missing" in IDL objects [message #67260] |
Fri, 17 July 2009 09:20 |
![Paul Van Delst[1] is currently offline](theme/default/images/xoffline.png.pagespeed.ic.XRkd1fkXye.png "Paul Van Delst[1] is currently offline")
Paul Van Delst[1]
Messages: 1157
Registered: April 2002
|
Senior Member |
|
|
Hello,
I'm stringing together a bunch of different objects into a container. When I define
objects I always define an "Inspect" method so I can have a lookee at the internals of the
objects (like the ruby inspect method). However, the inspect method for the container
simply loops over the objects that have been placed in it calling their inspect methods.
So, if I reach an object that does not have an inspect method, is there a technique to
pre-determine if I can even call the method to avoid the
% Attempt to call undefined procedure/function: 'OBJ::INSPECT'
error that I get?
Ruby provides a "method_missing" method to enable one to handle this sort of thing. Does
IDL have any sort of equivalent? Looking at the various ROUTINE_INFO, RESOLVE_ROUTINE
help, they don't appear to be that reliable.
cheers,
paulv
|
|
|
|
comp.lang.idl-pvwave archive
Members
Search
Help
Login
Home
