R
rio4ruby
I recently ran across a post regarding the warnings emitted when -w
is used with code using Rio. Personally, I find it unacceptable for Rio
to emit warnings.
The warnings of interest are:
useless use of > in void context
useless use of < in void context
My personal opinion is that Ruby is being presumptious. Once a
language allows a class to overload an operator, can it then
presume to know the context of its intended use? The language itself
uses '<' to indicate inheritance -- in a void context.
That is beside the point, however.
Is there a good way for a libray to silence these warnings without
masking client warnings? Is it simply a matter of setting $VERBOSE?
Thanks,
-Christopher
is used with code using Rio. Personally, I find it unacceptable for Rio
to emit warnings.
The warnings of interest are:
useless use of > in void context
useless use of < in void context
My personal opinion is that Ruby is being presumptious. Once a
language allows a class to overload an operator, can it then
presume to know the context of its intended use? The language itself
uses '<' to indicate inheritance -- in a void context.
That is beside the point, however.
Is there a good way for a libray to silence these warnings without
masking client warnings? Is it simply a matter of setting $VERBOSE?
Thanks,
-Christopher