in reply to syswrite numbers, not strings

I don't see anything bizarre about it. 
$ perl -E 'say 0x65'
101

[download]
This is how integers get promoted to strings. Why is that unexpected? People would get confused if they typed perl -E 'say 2 + 2' and got 'end of transmission' byte.

Perhaps you mean that syswrite should be special and different from say, print... I don't agree, consistency is a good thing

Replies are listed 'Best First'.
Re^2: syswrite numbers, not strings
by akujbida (Acolyte) on Dec 18, 2014 at 11:54 UTC
    Perhaps I just like variables to be firmly typed, so I can stand on them without wobbling. Bizarreness is defined by point of view, so we can certainly have different bizarres. I don't think I said anything to imply that a special case need exist. I like your print 0x65 example.
[reply]

      While you could try using a module like Variable::Strongly::Typed, it probably would be of little help. As best I can tell, Variable::Strongly::Typed, only prevents you from assigning the wrong type of value to variables. It does not try to prevent implicit stringification of numbers nor numification of strings. Also, the documentation implies it uses a regex to determine if a value is a number.

      There is also typesafety, but the documentation says it's for objects, so it may also be of little help.

      Also, there is PerlGP, which claims to provide strong typing. Never heard of it before now, so I don't know just what it provides.

[reply]

In Section Seekers of Perl Wisdom