Re: pdd03 (calling conventions) revised; get_params vs. READONLY

2005-11-30 Thread Chip Salzenberg
On Wed, Nov 30, 2005 at 10:57:26AM -0800, Jonathan Sillito wrote: > What is the status of the todo's mentioned in the BUGS section, who > is working on these -- I am looking for a place to jump in. Also > what is the status of the exception subsystem you mentioned? All those TODOs are for design,

Re: pdd03 (calling conventions) revised; get_params vs. READONLY

2005-11-30 Thread Jonathan Sillito
On 11/29/05, Chip Salzenberg <[EMAIL PROTECTED]> wrote: > I've reviewed pdd03 and brought it back from pdds/clip. Thanks for reviving this document Chip. Way back when I implemented some of the original lexical and calling code (like the scratchpad -- may it rest in peace). What is the status of t

Re: pdd03 (calling conventions) revised; get_params vs. READONLY

2005-11-30 Thread Roger Browne
Chip Salzenberg wrote: > Most importantly, I've proposed (but not mandated) a get_params flag > called "READONLY", which automatically creates a read-only wrapper > around a PMC parameter. I'd use READONLY if it existed, though I can get by without it. Regards, Roger Browne

pdd03 (calling conventions) revised; get_params vs. READONLY

2005-11-29 Thread Chip Salzenberg
I've reviewed pdd03 and brought it back from pdds/clip. Mostly it's the same as before, albeit with clarifications and a few flag bits renamed to match PIR. I have made a couple actual changes, though. On the small side, there's a barest hint of named parameters. Most importantly, I've proposed