Ticket #159 (closed deprecation: fixed)

Opened 11 years ago

Last modified 10 years ago

named class/pmc lookup in pir syntax such as new, isa, subclass, get_class, etc [post 0.9.0]

Reported by: coke Owned by: whiteknight
Priority: normal Milestone:
Component: core Version:
Severity: medium Keywords:
Cc: Language:
Patch status: Platform:

Description

From DEPRECATED.pod:

Class PMC name resolution will be the following.

if the arg is a STRING
  Relative to the current Namespace

if the arg is a ResizableStringArray  
  Relative to the current HLL Namespace

if the arg is a Namespace or Class PMC
  The passed in class or the class attatched to the passed in namespace.

Change History

Changed 11 years ago by pmichaud

Does this imply that keys are no longer usable for class lookups? If so, then -1.

Pm

Changed 11 years ago by whiteknight

Yes, can we get some clarification on this? Are keys allowed to specify a class name? If so, what are the keys relative to? We need an answer on this before we can reasonably resolve this.

Changed 11 years ago by allison

  • milestone changed from 1.0 to 1.1

Yes, keys are still allowed for a class name lookup, they have the same behavior as a ResizableStringArray (or FixedStringArray): lookup relative to the current HLL namespace.

Moving to the 1.1 milestone.

Changed 11 years ago by whiteknight

  • status changed from new to assigned
  • owner set to whiteknight
  • milestone changed from 1.3 to 1.5

Changed 11 years ago by jkeenan

  • component changed from none to core

Changed 11 years ago by allison

This ticket needs specific tasks (which internal functions should be modified and how).

Changed 11 years ago by whiteknight

  • milestone 1.5 deleted

Changed 10 years ago by coke

  • type changed from todo to deprecated
  • summary changed from Deprecated: named class/pmc lookup in pir syntax such as new, isa, subclass, get_class, etc [post 0.9.0] to named class/pmc lookup in pir syntax such as new, isa, subclass, get_class, etc [post 0.9.0]

Changed 10 years ago by whiteknight

  • status changed from assigned to closed
  • resolution set to fixed

Got this reply from pmichaud:

<pmichaud> Whiteknight: looks like it was decided that class lookups would always be relative to the current HLL namespace (TT #8, http://lists.parrot.org/pipermail/parrot-dev/2009-January/000863.html, TT #159 comment #3)

So, the greater issue appears to have been resolved, the proposal discussed here was poo-poo'd and there arne't enough details given to pursue an additional course of action, if any are needed. Closing ticket.

Note: See TracTickets for help on using tickets.