On Sun, 4 Dec 2005, Joshua Hoblitt wrote:
What still needs to be done:
- CLI options need some minor tweaks
I think they need some major design. In particular, it would be
nice to have a documented consistent interface to setting or
unsetting various things. Then, it would be *very* nice
On Sun, Dec 04, 2005 at 06:37:25PM +0100, Leopold Toetsch wrote:
This is an unordered collection of my thoughts towards a next release:
* config module cleanup: auto/jit.pm and gen/icu.pm comes to my mind
(and why /gen anyway?)
Not just the steps themselves need work, there is still some
Leopold Toetsch [EMAIL PROTECTED] wrote:
* interfaces: start some brainstorming, what we might need in Parrot core
Having these would be great for the work I'm doing on the .NET = PIR
translator. Also I would really like to have support for:-
* Static methods
* Class level attributes
On 12/5/05, Joshua Hoblitt [EMAIL PROTECTED] wrote:
Not just the steps themselves need work, there is still some fairly
substantial work left to be done on the configure framework as part of
my refactoring project. This has been going rather slowly because it's
usually bad to major radical
This is an unordered collection of my thoughts towards a next release:
* namespaces: create a PDD based on Matt's document
* interfaces: start some brainstorming, what we might need in Parrot
core
* bytecode library loading: needs rewriting and major cleanup
* config module cleanup:
Something else?
I would be pleased to have a design decision made regarding inheritance
of attributes in Parrot objects.
See the last few comments here:
https://rt.perl.org/rt3/Ticket/Display.html?id=36411
for the design questions that arose.
Regards,
Roger Browne
