Re: [freeelks-devel] {ANY}.io

[Emmanuel S. [ES] <ma...@ei...>]

> That's what I suspected as well. Clearly removing io from ANY would
> break backward compatibility. But the break would be rather mild, if
> acompanied by the provision of a class STANDARD_IO (I have just picked a
> name), which provides io. The classes which use io simply would have to
> insert "inherit STANDARD_IO" into its text and everything would work
> smoothely (just editorial work, no risk to have any semantic problem).
> 
> But anyhow, thank you for your feedback.

It is going to be hard to remove it from ANY. One of Bertrand's reason for keeping
it in ANY is for teaching. You can write the hello world example without learning
about inheritance. You only need to know that there is this special thing called
`io'. 

People may or may not agree on this, but that the state of the affair.

Regards,
Manu