Lightning flashed, thunder crashed and Larry Wall <[EMAIL PROTECTED]> whispered: | I'm thinking concat will be ~. Furthermore, I'm thinking unary ~ will | be stringify, and unary ^ will be bit complement, on the theory that | bit complement is like xoring with 0xffffffff. And unary + will be a | numify, not a no-op. How difficult would it be to co-opt , for concat? Currently it doesn't do much of value in a strictly scalar context. It is also already fairly synonymous in a string context: print "a", $x, "$b"; Hmmm... this could be a real problem in list context though. I suppose it is conceivable that someone might want to do something like: @a = ( $a . $b , $c ); Maybe not a good idea. But maybe something to think about. -spp
- Re: Tying & Overloading Graham Barr
- Re: Tying & Overloading Davíð Helgason
- Re: Tying & Overloading John Porter
- Re: Tying & Overloading Simon Cozens
- Re: Tying & Overloading John Porter
- Re: Tying & Overloading Dan Sugalski
- Re: Tying & Overloading Dan Sugalski
- Re: Tying & Overloading Simon Cozens
- Re: Tying & Overloading Graham Barr
- Re: Tying & Overloading Larry Wall
- Re: Tying & Overloading Stephen P. Potter
- Re: Tying & Overloading Dan Sugalski
- Re: Tying & Overloading David L. Nicol
- Re: Tying & Overloading Stephen P. Potter
- Re: Tying & Overloading Nathan Wiger
- Re: Tying & Overloading Larry Wall
- Re: Tying & Overloading Austin Hastings
- Re: Tying & Overloading Austin Hastings
- Re: Tying & Overloading Larry Wall
- Re: Tying & Overloading Glenn Linderman
- Re: Tying & Overloading Larry Wall