* OO "void *user_data" in thick library bindings
@ 2014-07-24 16:56 Victor Porton
0 siblings, 0 replies; only message in thread
From: Victor Porton @ 2014-07-24 16:56 UTC (permalink / raw)
Is it a good idea in thick bindings for a C library to replace every handler
with user data:
void (*raptor_statement_handler) (void *user_data, *statement);
with a tagged record whose (or its descendant) access is ALWAYS passed as
user_data? (I mean in my bindings NEVER pass anything other than a
descendant of my tagged record as user_data. Huh?)
This is object oriented, but maybe a little restrictive. Well, if it would
be object oriented from the beginnings, it would probably be the way to
implement it. So, it is probably not too restrictive.
--
Victor Porton - http://portonvictor.org
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2014-07-24 16:56 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2014-07-24 16:56 OO "void *user_data" in thick library bindings Victor Porton
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox