Ticket #2111 (new deprecation)

Opened 11 years ago

Last modified 10 years ago

new_s and new_s_i opcodes

Reported by: whiteknight Owned by:
Priority: trivial Milestone: 3.9
Component: core Version: master
Severity: low Keywords: string
Cc: Language:
Patch status: Platform: all

Description

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.

Change History

in reply to: ↑ description   Changed 11 years ago by 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

  Changed 11 years ago by jkeenan

  • milestone changed from 3.6 to 3.9

  Changed 10 years ago by 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

Note: See TracTickets for help on using tickets.