Thorsten Ottosen wrote:
Yes, the upcomming revision will fix this somehow without breaking
exisiting code.
Good luck with that. I don't know how your going to get two default
constructors that do different behaviors.
Will this fix be in the 1.44 release?
Ryan
