|
Boost : |
From: John Torjo (john.lists_at_[hidden])
Date: 2004-07-26 04:21:26
Vladimir Prus wrote:
> Hi Mattias,
>
>>On Fri, 23 Jul 2004 13:49:22 +0400, Vladimir Prus <ghost_at_[hidden]> wrote:
>>
>>>static imported_function<void()> apiFunc( "ApiFunc", "OSLib" );
>>
>>Couldn't find a nice point in the thread at which to insert this
>>comment, so I'll just spit it out: Since we have both the name of the
>>function and the function type, and given that a lib such as this
>>should provide a platform-independent interface, would it be useful if
>>the library automatically mangled the name according to the type?
>
>
> I think you've missed something ;-) Even my initial reply inthe "additional
> boost libraries" thread mentioned the possibility of calling functions which
> are not "extern "C". At least two other persons seems to want this. I find
> this would be nice, though not critical at all.
>
At this point, I'm satisfied if the one who implements this library
allows "extern C" functions only - perhaps for the non-extern C ones, in
a future version. (otherwise, I think it would take too much to implement)
Best,
John
-- John Torjo Freelancer -- john_at_[hidden] Contributing editor, C/C++ Users Journal -- "Win32 GUI Generics" -- generics & GUI do mix, after all -- http://www.torjo.com/win32gui/ Professional Logging Solution for FREE -- http://www.torjo.com/code/logging.zip (logging - C++) -- http://www.torjo.com/logview/ (viewing/filtering - Win32) -- http://www.torjo.com/logbreak/ (debugging - Win32) (source code available)
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk