Re: version 4 conflicts
- Posted by jimcbrown (admin) Aug 11, 2013
- 1421 views
SDPringle said...
Devs: suppose we rewrite the include/*.e files so they public include the symbols expected from std/*.e. Wouldn't this solve this problem better than needing to add this without statement?
It would fix this particular problem more elegantly, but open up a new can of worms - we'd need to find a way to selectively public include only the symbols desired, and avoid exporting any new 4.0+ symbol names. Otherwise, we might break compatibility with older code that makes use of those symbol names.
