SharedLib.getSymbol(char*)

bobef Joined: 06/05/05 Posts: 86

Posted: 03/05/08 18:43:24 Hi, I think this is wrong, but I don't know if I should create a ticket. Why SharedLib?.getSymbol is accepting char*, instead of char[]? This is not very D-ish. Maybe there is some compatibility (or other) reason that I am not aware of that prevents using toStringz inside getSymbol?

Author	Message
h3r3tic Joined: 03/30/04 Posts: 6	Posted: 03/05/08 20:32:26 Heya! Thanks for mentioning this. It initially had two overloads of getSymbol, but then you had to say "foo".ptr or "foo"[] to select the overload. Folks didn't like that either... It currently uses char* instead of char[] in order not to abuse the GC and just be a thin wrapper over the system facilities. Usually getSymbol will be used with literals as args, so char* is fine then. Yet I see you're building the symbol name string using some D code magic. I guess another function might be added if it's so desired. Any suggestions for the name? An overload is out of question, unfortunately.
bobef Joined: 06/05/05 Posts: 86	Posted: 03/06/08 05:28:42 char* is fine for me, I just noticed :)
svanleent Joined: 09/25/04 Posts: 8	Posted: 03/13/08 10:07:37 I see, no overload. Ok perhaps SharedLib?[char[]]? (so using the opIndex(char[]) function) How C++ became ancient