[dumael]

I'll freely admit I'm not a fan of dynamic languages (mostly due to hacking the Erlang HiPE compiler) and in a previous life I was a Haskell guy. So I'm a fan of strict typing.

> The unreasonable behavior is giving integers as strings.

That I can agree with. But in that case this notion of reusing '+' as string concatenation but '-' is coercing strings to integers is utterly bizarre.

I'm afraid to ask what '*' does (string replication?) and '/' "space magic"?

[Nadya]

I absolutely prefer strict typing myself. The issue becomes whether or not one thinks type coercion should be a thing.

I'm personally against type coercion - but I also understand how it functions (and why it functions). I disagree with the "why" but as long as I understand the "how" I can avoid gotchas like string coercion. :)

Multiplication ( * ) and division ( / ) coerce to integers. Only + is used for strings, particularly concatenation. Personally I'm a fan of & being used for string concatenation and can't think offhand why not to use it, other than slight possibility of confusion over &&. However I'm not aware of a language that uses it.

  >>"5" * 5
  25
  >>"5" * "5"
  25
  >>"5" / 5
  1
  >>"5" / "5"
  1

[dumael]

> I absolutely prefer strict typing myself. The issue becomes whether or not one thinks type coercion should be a thing.

As a strong typing fanatic, I'd rather have the interpreter/compiler scream at me. In my opinion automatic type coercion is slightly less wrong than undefined behavior in C.

(Aside, did you know that if GCC spots a statically provable null pointer deference, it will insert __builtin_trap() after the deference? I didn't know either until yesterday. This is acceptable because undefined behavior can mean "eat you hard drive".)

If for strings '+' is concatenation, and '*' is for replication with '-' and "/" as exception behavior I can fully understand. (Admittedly '+' over '&' is either style or hard-core "the operation is different, therefore we need a different symbol choice").

Your example worries me. Personally I would not design a language like that.

(Though I may have abused it in the past.)

[Nadya]

>Admittedly '+' over '&' is either style or hard-core "the operation is different, therefore we need a different symbol choice

The former more than the latter. The operation is different therefore we need a different symbol choice - and & also makes as much sense stylistically as + does.

"string1" and "string2", when read, makes sense. & is different from the conditional && like piping | is different from the conditional or ||

>Your example worries me. Personally I would not design a language like that.

Neither would I, but I like to think it was part of "made in 10 days" that allowed it to stick around.

[dragonwriter]

> "string1" and "string2", when read, makes sense. & is different from the conditional && like piping | is different from the conditional or ||

Of course, in languages where & and | are already in use for bitwise operations on ints (etc.), using & for string concatenation would be a different form of the same clash as using + is.

[marcosdumay]

> I'm afraid to ask what '*' does (string replication?)

In Python it does. But then, Python has strong types and won't coerce the strings to numbers for '-', what makes this sane.