Ticket #1662 (new RFC)

Opened 12 years ago

Last modified 11 years ago

Should NameSpace entries be available through a hash-like interface?

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


Several notes I've run across make references to the fact that NameSpace PMCs should be searchable using a hash-like interface to find entries in the namespace. There aren't a lot of details in these spattered notes, so I don't know whether it suggests we should be able to lookup nested namespaces using such an interface, or NameSpace global entries, or both.

Here's an example of a note from src/global.c:

NOTE: At present the use of the {get, set}_global functions is mandatory due
      to the wacky namespace typing of the default Parrot namespace.
      Eventually it will be safe to just use the standard hash interface
      (if desired).

Let's figure out exactly what these notes mean, what we want the NameSpace interface to be, and make everything right.

Change History

Changed 11 years ago by jkeenan

  • component changed from none to core

Has anyone had further insights on this topic?

Thank you very much.


Note: See TracTickets for help on using tickets.