[gs-bugs] [Bug 689698] scan_token symbol might collide with other libraries
bugzilla-daemon at ghostscript.com
bugzilla-daemon at ghostscript.com
Wed Jan 12 21:32:27 UTC 2011
http://bugs.ghostscript.com/show_bug.cgi?id=689698
--- Comment #11 from Diego Pettenò <flameeyes at gmail.com> 2011-01-12 21:32:22 UTC ---
Henry I guess the answer is "Ralph wouldn't bother even listening to me until
an application crashed", and after not being listened to I really couldn't get
myself to create an artificial example of an application miscalling the
functions. As it happens, Evince did so already.
In general yes I suggest you do prefix all the exported symbols with something
like gs_, maybe gs_x_ or something for those that are not supposed to be used
(and that could also help you as GNU ld, Apple's and (I think) Sun's allows you
to hide symbols from the public table based on their prefix — not a problem for
Windows since there you have to list explicitly what you do export).
The less generic a symbol name is the less likely it is to collide (and lead to
crashes at one point or another).
--
Configure bugmail: http://bugs.ghostscript.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
More information about the gs-bugs
mailing list