This is my 1st post to this ML,
I read 'bout a problem: (false || not(true))
in a place, and made a little considerations.
I give NOW, the source code AsIs,
with the ‘comments’ in itâ€¦
#!/usr/bin/env ruby -Ku
elsif !c # c == false || not true
puts "case1: ", c
It’s just NO problem, in C-programmer fashion [not fully tested]
c == false || not true if you want it to be TRUE, before that,
#elsif c.class == Boolean or
#elsif c.class != Char or something, you must ask.
1st of all, have WE Classes like Boolean or Char ???
elsif c.class != String # now this line may be wrong questionâ€¦
puts "case2: c is no String"
puts "case2: ", c
c = STDIN.getc()
Was it just Me? that
got troubled with needless TRUE
in evaluating True-False, aString(or aChar) AsIsâ€¦
2 bits thinking helps 66.7%
Shindo Motoaki (Motoakira)