On 2020-05-18 14:35, Peter Pentchev wrote:
My point is that you put a bare "say" without telling it*what* to say,
which does something quite specific in both Perl and Raku. That should,
at least, explain the error-like message.
G'luck,
Peter
What I was after was to see what impact I had coercing a
Bool to a Bool verses coercing a half a Bool and unless
text message to a Bool.
But, you know, I am using a (very) high lever language
for a reason. I can get to the final product twice as
fast. If I wanted to optimize the use of my CPU, I would
program in C, or if I was REALLY masochistic, I program
in Assembly. (Done that, don't want to do it again!)
So my little coercing Bool to Bool so I do not have to
remember which IO.soemletter is or is not returning an
actual Boolean is a mute point. I am already wasting
a ton of CPU by being in a high level language to start with.
And I don't care. My computer is a bazillion times more powerful than
any thing I waste on a high level language.
It hardly notices my "indiscretion"
An gee wiz, Raku is a TON more human readable than C,
which gives me a migraine if I stare at it too long.
Raku is far more maintainable. But that is just my opinion
