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 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 radic
"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 (as
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 fa
> 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
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: auto/jit.
Leopold Toetsch wrote:
- please test on all available platforms and 'make smoke' and/or
update PLATFORMS
With the recent Stash changes and (I presume) a fix to avoid reloading
pbc files, we're passing all tests on HP-UX!
Something's happened to spoil languages in the last day, but I don't b
The next release is due this weekend. I'll start release procedure at
Sun 4th, ~13:00 UTC.
The usual terms apply:
- no bigger changes to Parrot core, especially nothing that could break
the build or Parrot
- please test on all available platforms and 'make smoke' and/or up
The next release 0.3.1. will happen at Sun 6th. I'll start the release
procedure around 12:00 UTC - please no checkins at all after this time
until further notice.
There is kind of a feature freeze from now on, which means: please make
sure that nothing breaks. Parrot corrently tests 10
At 07:50 AM 3/7/2005, Leopold Toetsch wrote:
Roger Browne <[EMAIL PROTECTED]> wrote:
> On Mon, 2005-03-07 at 11:01 +0100, Leopold Toetsch wrote:
>> 4.1.1) implement a language pragma in assembler, e.g.:
>>
>> .HL_language Python
Sounds good to me except that I would prefer you remove the HL_
and
Roger Browne <[EMAIL PROTECTED]> wrote:
> On Mon, 2005-03-07 at 11:01 +0100, Leopold Toetsch wrote:
>> 4.1.1) implement a language pragma in assembler, e.g.:
>>
>> .HL_language Python
> A pragma like that seems to split high-level languages into two groups:
> those that are specially known to p
es, and would create a BirdCharacter if the calling
language was "Bird", but would create a PyInt if the calling language
was "Python".
I hope this makes some sense, and that you can see some merit in it.
> Proposed steps towards the next release 0.2 and beyond.
I'd be
Below inline/attached is a proposal for Parrot core changes. I'll post a
more detailed proposal for 1) objects in a minute.
leo
Proposed steps towards the next release 0.2 and beyond.
These are numbered just for reference but are else in no particular
order. A lot can be done in parallel.
While I realize that Leo's doing conference stuff at the moment, I'd
like to start thinking about the next release. For this, I think I'd
specifically like to shoot for the redo of classes/ -- getting all
the PMCs we *want* actually in and working, and the ones we don'
14 matches
Mail list logo
