new_s and new_s_i opcodes

[Whiteknight]

We have two opcodes for creating new, empty strings: new_s and new_s_i (both in src/ops/string.ops). There is a note in that file:

XXX: Do these ops make sense with immutable strings?

My answer is "no".

We should deprecate and remove these ops because they are worthless now.

Originally http://trac.parrot.org/parrot/ticket/2111

[jkeenan]

Replying to whiteknight:

We have two opcodes for creating new, empty strings: new_s and new_s_i (both in src/ops/string.ops). There is a note in that file:

We should deprecate and remove these ops because they are worthless now.

Given the problem we've had with deprecations in recent days, I feel we should ask:

Which projects built on top of Parrot use these opcodes?

If there are such usages, what is our migration plan?

Thank you very much.

kid51

[bacek]

Hello.

 https://github.com/parrot/parrot/issues/203

new_s_i is deprecated.

new_s should stay to avoid null pointer exception little bit more easily.

-- Bacek

[Whiteknight]

new_s_i does not appear to exist anymore. new_s, as requested by bacek, can stay. I'm closing this ticket now.