| I note that many compilers now support an "exports" list so you can
| explicitly control which of your symbols are exported, and is generally
| limited to the advertised API. This seems like the right model.
its definitely the way to go, but my impression was that gcc/ld didn't support
such things on linux yet (please correct me if i'm wrong), so i'm
just trying to encourage things to be better from the start. Windows
drives me crazy with the amount of namespace pollution microsoft dumped
in it (my personal favourite is random include files that #define things
like g1 and g2).
-db
