Release: Parrot 0.4.7, "Caique"

2006-11-14 Thread Chip Salzenberg
g Subversion or SVK to access our source code repository; see instructions at http://www.parrotcode.org/source.html . Thanks to all our contributors for making this possible, and our sponsors for supporting this project. Share & Enjoy! -- Chip Salzenberg <[EMAIL PROTECTED]>

All Parrot coders: Please check NEWS, release is soon

2006-11-13 Thread Chip Salzenberg
space refinements + Coroutine improvements + An impressive swarm of other bugfixes and enhancements -- Chip Salzenberg <[EMAIL PROTECTED]>

Re: Coding Standard Questions

2006-11-12 Thread Chip Salzenberg
On Tue, Oct 17, 2006 at 11:41:06PM +0200, Leopold Toetsch wrote: > Anything that has the smallest smell of ever needing an extra statement after > if or else shall use braces in the first place (IMHO). Predicting the future is something humans are bad at, sadly. -- Chip Salzenberg &

Re: Coding Standard Questions

2006-11-12 Thread Chip Salzenberg
this is the preferred format: if (foo) bar(); else baz(); -- Chip Salzenberg <[EMAIL PROTECTED]>

Re: Coding Standard Questions

2006-11-12 Thread Chip Salzenberg
work in your initializations, work that may be entirely pointless if the given function takes an early return for some reason. -- Chip Salzenberg <[EMAIL PROTECTED]>

Re: r15330 - in trunk: . compilers/imcc docs docs/pdds include/parrot src

2006-11-11 Thread Chip Salzenberg
rays are not flattened. Is it OK to just > flush it? I've now done so, thanks. -- Chip Salzenberg <[EMAIL PROTECTED]>

pls ignore commits w/o content

2006-09-06 Thread Chip Salzenberg
It seems that I've managed to confuse svk again, as it continues to re-commit old log messages with no content. -- Chip Salzenberg <[EMAIL PROTECTED]>

Re: String.to_int() vs. opcode

2006-08-25 Thread Chip Salzenberg
rhaps I should let that go unmentiond. Oops, too late. ("Bitter? Oh, a *tad*.") > I do think pulling too hard at this thread might require a closer look at > what's current in src/pmc/ vs. src/*.c vs src/ops/ (where's there's > smoke...): a lot of the current state

String.to_int() vs. opcode

2006-08-25 Thread Chip Salzenberg
METHOD becomes redundant. -- Chip Salzenberg <[EMAIL PROTECTED]>

Re: End the Hollerith Tyranny? (linelength.t)

2006-08-21 Thread Chip Salzenberg
On Mon, Aug 21, 2006 at 06:05:08PM -0400, Mr. Shawn H. Corey wrote: > Don't forget that some programs, like mailers, wrap at 80 characters. I don't know of any mailer that is hard-coded at any given column width. Do you? -- Chip Salzenberg <[EMAIL PROTECTED]>

Re: End the Hollerith Tyranny? (linelength.t)

2006-08-21 Thread Chip Salzenberg
you. My school's punch card machines were in the same room as the TRS-80 Model I ("THE COMPUTER ROOM"). These kids today with their hula hoops and fax machines and intarwebs... -- Chip Salzenberg <[EMAIL PROTECTED]>

Re: End the Hollerith Tyranny? (linelength.t)

2006-08-21 Thread Chip Salzenberg
Some selectivity is in order, or we'll have to target 1989 memory sizes, disk capacities, and network bandwidth PS: Allison gets to specify the doc formatting, if she likes. Exceptions are technically trivial. See the bottom of the pdds for how a given file can override the default word wrap column. -- Chip Salzenberg <[EMAIL PROTECTED]>

Re: SKIPs Are Now a Code Smell

2006-08-21 Thread Chip Salzenberg
ible, and > delete the tests that don't matter anymore. I'm Chip Salzenberg, and I approve of this message. > I've just checked in a CAGE task for this. Thanks. -- Chip Salzenberg <[EMAIL PROTECTED]>

End the Hollerith Tyranny? (linelength.t)

2006-08-21 Thread Chip Salzenberg
, this is NOT a style preference question. The only reason I'm bugging the list with this question is to solicit stories of "80 columns are the max supported by ". adTHANKSvance -- Chip Salzenberg <[EMAIL PROTECTED]>

Re: [perl #40204] line numbers of runtime errors are one too low

2006-08-20 Thread Chip Salzenberg
et was right. Besides, it's not like they aren't a renewable resource. :-) -- Chip Salzenberg <[EMAIL PROTECTED]>

Re: None Is Dead

2006-08-17 Thread Chip Salzenberg
{ not replying to the ticket } On Fri, Aug 18, 2006 at 01:10:07AM +0200, Leopold Toetsch wrote: > Am Donnerstag, 17. August 2006 08:24 schrieb Chip Salzenberg: > > The None class serves no useful (portable) purpose and it should be > > removed, especially from the public in

Re: [perl #40178] None Must Die

2006-08-17 Thread Chip Salzenberg
direct way to indicate an error when the output type has no out-of-band values, like INTVAL. And exceptions are still too expensive. So at present I'd consider this a misbug. -- Chip Salzenberg <[EMAIL PROTECTED]>

Re: [perl #40178] None Must Die

2006-08-17 Thread Chip Salzenberg
$P0 = new .Undef ... $P1 = default hsh['key1'], $P0 $P1 = default hsh['key2'], $P0 ... It would work without the lookups too: $S0 = default $S0, ''# if $S0 is null, assign it '' what say? -- Chip Salzenberg <[EMAIL PROTECTED]>

Re: [perl #40178] None Must Die

2006-08-17 Thread Chip Salzenberg
On Thu, Aug 17, 2006 at 12:13:30PM -0700, Leopold Toetsch via RT wrote: > Am Donnerstag, 17. August 2006 08:24 schrieb Chip Salzenberg: > > The None class serves no useful (portable) purpose and it should be > > removed, especially from the public interface of Hash. > > I&#

[perl #40065] STM first merge tracking ticket

2006-08-17 Thread Chip Salzenberg via RT
first merge done. yeah baby

stm ready (was Re: More review of current stm branch code)

2006-08-15 Thread Chip Salzenberg
So, given the below, looks like we've got everything sewn up and the long-awaited day of the STM merge is upon us. Charles, care to do the honors? On Tue, Aug 15, 2006 at 06:31:38PM -0400, Charles Reiss wrote: > On 8/15/06, Chip Salzenberg <[EMAIL PROTECTED]> wrote: > >On Sat

Re: More review of current stm branch code

2006-08-15 Thread Chip Salzenberg
. > The hard part of doing it correctly is handling inheritance. It's an interface guarantee, and as such I think it's OK that it can't be overridden in a derived class. Agree? > >A bigger issue for automatic read-only variant generation is that MMD > >methods curren

Re: More review of current stm branch code

2006-08-15 Thread Chip Salzenberg
On Fri, Aug 11, 2006 at 04:38:59PM -0400, Charles Reiss wrote: > On 8/10/06, Chip Salzenberg <[EMAIL PROTECTED]> wrote: > > /* XXX is it okay to combine flatten/slurpy into one flag? */ > > > > The answer is "No": "flat" is an output flag, &qu

Re: Review of current stm branch code

2006-08-11 Thread Chip Salzenberg
ment.[*] If people kept talking about it, and if I kept trying to persuade them, back & forth... then, it'd be an argument. [*] It's abuse. Arguments are down the hall. -- Chip Salzenberg <[EMAIL PROTECTED]>

Re: Review of current stm branch code

2006-08-10 Thread Chip Salzenberg
On Thu, Aug 10, 2006 at 07:11:15PM -1000, Joshua Hoblitt wrote: > On Thu, Aug 10, 2006 at 07:19:21PM -0700, Chip Salzenberg wrote: > > * useless curlies > >OTGH, the project needs automated filters for more coding standards, > >including one that that notes (and

More review of current stm branch code

2006-08-10 Thread Chip Salzenberg
HER NAMING THING * Please rename 'ro_variant' to something ending in '_vtable', e.g. 'ro_variant_vtable', to make clear that it's not a class pointer or type number. -- Chip Salzenberg <[EMAIL PROTECTED]>

Review of current stm branch code

2006-08-10 Thread Chip Salzenberg
nterp" -void pt_thread_prepare_for_run(Parrot_Interp d, Parrot_Interp s); +void pt_thread_prepare_for_run(Parrot_Interp d, const Parrot_Interp s); What's the purpose of this? It doesn't protect *s from changes. [time passes] I now see that some of the existing functions already have this construct. Perhaps you were just imitating them? -- Chip Salzenberg <[EMAIL PROTECTED]>

Parrot 0.4.6 Released!

2006-08-09 Thread Chip Salzenberg
elop on Parrot (or help develop Parrot itself), we strongly recommend that you keep up with the latest and best Parrot code by accessing our source code repository. Instructions for doing this are at <http://www.parrotcode.org/source.html>. I'd like to thank all our contributors for making this possible, and our sponsors for supporting this project. Share & Enjoy! Chip Salzenberg <[EMAIL PROTECTED]>

can somebody convert an MS Project 97 file for me?

2006-08-09 Thread Chip Salzenberg
If you have MS Project 98 or Project 2000 installed, and can load-and-save a project file for me, please mail me. adTHANSKvance -- Chip Salzenberg <[EMAIL PROTECTED]>

Parrot 0.4.6 Released! {p2-only announcement}

2006-08-08 Thread Chip Salzenberg
y accessing our source code repository. Instructions for doing this are at <http://www.parrotcode.org/source.html>. I'd like to thank all our contributors for making this possible, and our sponsors for supporting this project. Share & Enjoy! Chip Salzenberg <[EMAIL PROTECTED]>

Re: [perl #39856] TODO: Produce Single PBC from Multiple PIR Files with -o

2006-08-08 Thread Chip Salzenberg
ow multiple :load routines. That's a bug, Shirley. > What we're looking for is more of a Parrot version of .par/.jar/.pkg: > bundle up all the files you need for a particular application into a > single file. Not a PBC, but some form of "archive" or "package" format. I don't see any harm in .zip and .tar and [archive method of choice] plugins. -- Chip Salzenberg <[EMAIL PROTECTED]>

svk is generating almost-empty change sets

2006-08-04 Thread Chip Salzenberg
FYI, the change sets you're seeing that have only modifications to the meta info for 'trunk' are being generated by 'svk push', and I don't know why. But they seem harmless enough. -- Chip Salzenberg <[EMAIL PROTECTED]>

Impending release of Parrot 0.4.6

2006-08-03 Thread Chip Salzenberg
Parrot 0.4.6 will be released Real Soon Now, probably this weekend. No code slush will be needed ... assuming I can manipulate Subversion to my will and create a release branch. Smokes and PLATFORMS would welcome your attention. -- Chip Salzenberg <[EMAIL PROTECTED]>

[perl #39750] [EMAIL PROTECTED]: tru64 core dump: t/examples/japh_12.pasm

2006-08-03 Thread Chip Salzenberg via RT
Fixed in svn by deleting that never-will-work-again japh, which hacked internals in an amazingly evil way.

[perl #39751] unbug - [EMAIL PROTECTED]: tru64 core dump: t/dynoplibs/myops_4.pir

2006-08-03 Thread Chip Salzenberg via RT
parrot obeys you when you ask it politely to halt and catch fire

[perl #39752] [EMAIL PROTECTED]: tru64 core dump: t/op/lexicals_27.pir

2006-08-03 Thread Chip Salzenberg via RT
Fixed in svn. Actual bug was causing malloc(0). Proximate bug is that, on tru64, malloc(0) fails. :-)

[perl #39753] [EMAIL PROTECTED]: tru64 core dump: t/pmc/io_1.pir

2006-08-03 Thread Chip Salzenberg via RT
Until we know what these I/O ops should do, seg faults aren't unexpected. Nor are they something we can meaningfully fix. This ticket now depends on the review of the I/O pdd.

[perl #39754] [EMAIL PROTECTED]: tru64 core dump: t/pmc/resizablebooleanarray_20.pasm

2006-08-03 Thread Chip Salzenberg via RT
This ticket now depends on ResizeableBooleanArray rewrite.

Re: [perl #39756] [EMAIL PROTECTED]: tru64 core dump: t/examples/japh_10.pasm

2006-08-03 Thread Chip Salzenberg
'', > libs='-lm -lutil -lpthread -laio -lrt -lgmp' > Dynamic Linking: > share_ext='.so', ld_share_flags='-shared -expect_unresolved "*" -O4 -msym > -std -L/p/lib', > load_ext='.so', ld_load_flags='-shared -expect_unresolved "*" -O4 -msym > -std -L/p/lib' > Types: > iv=long, intvalsize=8, intsize=4, opcode_t=long, opcode_t_size=8, > ptrsize=8, ptr_alignment=8 byteorder=12345678, > nv=double, numvalsize=8, doublesize=8 > -- Chip Salzenberg <[EMAIL PROTECTED]>

Re: [perl #39776] [BUG] PGE core dump

2006-08-03 Thread Chip Salzenberg
p in this case? Why not a thrown exception? (I ask to know whether I should try to fix this before 0.4.6) -- Chip Salzenberg <[EMAIL PROTECTED]>

Re: [perl #39926] :init attribute (was Re: Implement .loadlib pragma in IMCC)

2006-08-03 Thread Chip Salzenberg
cumenting these subroutine attributes. Ah, the PIR pdd rears its nonexistent head again. -- Chip Salzenberg <[EMAIL PROTECTED]>

Re: Parrot news: namespace ops good, (some) namespace methods bad; key-accepting ops

2006-08-03 Thread Chip Salzenberg
On Thu, Aug 03, 2006 at 11:18:04AM -0700, Allison Randal wrote: > Chip Salzenberg wrote: > > (And of course I repeat a gentle reminder that the old find_global and > > store_global opcodes will eventually [eventually!] go away, so convert > > to the {get,make}*namespace

Re: [perl #39778] Segfault when using a Namespace with an Iterator

2006-08-03 Thread Chip Salzenberg
So, is the namespace iteration working now ... at least enough to close the ticket that says "segfault" in large friendly lettes? -- Chip Salzenberg <[EMAIL PROTECTED]>

Re: [perl #39986] Create Default PackFile for New Interpreter (Parrot C API)

2006-08-03 Thread Chip Salzenberg
On Thu, Aug 03, 2006 at 12:05:13PM -0700, chromatic wrote: > On Thursday 03 August 2006 11:18, Chip Salzenberg wrote: > > The whole question of packfiles is something I hadn't approached before, > > and now that I have, I wonder: Why does a packfile needs to exist at all >

Re: Fix symbol table namespace pollution

2006-08-03 Thread Chip Salzenberg
On Thu, Aug 03, 2006 at 03:03:08PM -0400, Will Coleda wrote: > http://www.parrotcode.org/cage-cleaners/todo.html Hey, that's neat. > http://xrl.us/owsd (Link to rt.perl.org) Hey, that's neater! > Enjoy. Done, thanks. :-) -- Chip Salzenberg <[EMAIL PROTECTED]>

Re: Fix symbol table namespace pollution

2006-08-03 Thread Chip Salzenberg
task to cage/todo.pod. That would be fairly neat, actually. Searches should be easy since "cage" isn't a term of art in the Parrot source. A link on parrotcode.org to an appropriately pre-formatted search would improve the ease of use. -- Chip Salzenberg <[EMAIL PROTECTED]>

Re: Fix symbol table namespace pollution

2006-08-03 Thread Chip Salzenberg
On Thu, Aug 03, 2006 at 01:29:20PM -0500, Andy Lester wrote: > I am way out of tuits lately. Can you please add this to cage/ > todo.pod for me? Or someone? Already done. -- Chip Salzenberg <[EMAIL PROTECTED]>

Re: [perl #39986] Create Default PackFile for New Interpreter (Parrot C API)

2006-08-03 Thread Chip Salzenberg
answering. As for any further improvements, I fear they will have to wait for 0.4.7. PS: Cage cleaners should detect and possibly correct all that namespace pollution. Yuck. -- Chip Salzenberg <[EMAIL PROTECTED]>

[CAGE] Fix non-symbol-table namespace pollution in public headers

2006-08-03 Thread Chip Salzenberg
g to entertain exceptions or new conventions. It's OK for public headers might have non-public parts protected with C<#ifdef PARROT_IN_CORE>. Those non-public parts might #define shorter versions of the public symbols, e.g. C<#define foo Parrot_foo>. -- Chip Salzenberg <[EMAIL PROTECTED]>

[CAGE] Fix symbol table namespace pollution

2006-08-03 Thread Chip Salzenberg
Extern functions and variables must have names that begin with C. -- Chip Salzenberg <[EMAIL PROTECTED]>

Parrot news: namespace ops good, (some) namespace methods bad; key-accepting ops

2006-08-03 Thread Chip Salzenberg
#x27; opcode variants demonstrates the inherent ambiguity between class names and class PMCs; merely being a PMC or not isn't enough to distinguish the intent of specifying class vs. class name. (Keys are PMCs.) This should be resolved in a general way for all class-accepting opcodes. -- Chip Salzenberg <[EMAIL PROTECTED]>

"Parrot: Evolution v2" presentation

2006-07-27 Thread Chip Salzenberg
ip/journal/30455 where I link to the presentation which is at http://feather.perl6.nl/~chip/oscon06/OSCON06-ParrotEvolutionV2.pdf Share and enjoy! -- Chip Salzenberg <[EMAIL PROTECTED]>

new {get,set}*global opcodes from pdd21 are available

2006-07-24 Thread Chip Salzenberg
d. Convert when convenient, but don't tarry. Share & Enjoy! -- Chip Salzenberg <[EMAIL PROTECTED]>

Re: Namespace.get_namespace() vs. optional params

2006-07-24 Thread Chip Salzenberg
; focused on driving us toward a 1.0 release, and this isn't a necessary > feature. I've added a TODO ticket, in case somebody with spare tuits wanders by. > Let the yaks go unshaved, > Allison It is not I who am crazy -- it is I who am _mad_! -- Chip Salzenberg <[EMAIL PROTECTED]>

Parrot users: 'make realclean'

2006-07-24 Thread Chip Salzenberg
Just a note for those who don't watch the commit logs: (1) why don't you? :-) (2) you'll want to 'make realclean' and rebuild after you update next Share & Enjoy! -- Chip Salzenberg <[EMAIL PROTECTED]>

Re: [perl #39867] Configure.perl --maintainer should check flex/bison versions

2006-07-18 Thread Chip Salzenberg
On Tue, Jul 18, 2006 at 10:48:45AM -1000, Joshua Hoblitt wrote: > I believe ambs & I fixed this before the bug was filed. ;) Bugs fixed before they're filed? Now _that's_ a process failure mode I can live with! :-) -- Chip Salzenberg <[EMAIL PROTECTED]>

another item for the cage list: INTVAL_MAX etc.

2006-07-18 Thread Chip Salzenberg
INTVAL_MIN LONG_MIN #define INTVAL_MAX LONG_MAX ... etc. -- Chip Salzenberg <[EMAIL PROTECTED]>

flex/bison version for Parrot?

2006-07-18 Thread Chip Salzenberg
What versions of flex and bison will work now? I'd like to make Configure.perl (or perhaps the Makefile at runtime?) choke on --maintainer if the right versions aren't found. -- Chip Salzenberg <[EMAIL PROTECTED]>

get_root_namespace opcode vs. interpinfo {cage cleaners?}

2006-07-18 Thread Chip Salzenberg
Allison, I suppose that given get_root_namespace, that we should get rid of C? If that's true, then a good little cleanup task would be removing all usage of the latter and replacing it with the former. -- Chip Salzenberg <[EMAIL PROTECTED]>

Re: Source cleanup ideas (pending STM merge)

2006-07-17 Thread Chip Salzenberg
On Mon, Jul 17, 2006 at 09:38:22PM -0500, Andy Lester wrote: > I've dumped all your suggestions into cage/todo.pod. Thanks. That you're editing cage and herding the cage cleaners is a load off my mind. -- Chip Salzenberg <[EMAIL PROTECTED]>

Re: Parrot should limit its own stack usage?

2006-07-17 Thread Chip Salzenberg
ning test cases? Running the test suite (or at least most of it) under ulimit is indeed a good idea. Whoever jumps in on this, please be prepared to adjust the value as reports come in from the field. :-) -- Chip Salzenberg <[EMAIL PROTECTED]>

Source cleanup ideas (pending STM merge)

2006-07-17 Thread Chip Salzenberg
nterp,a,b,c) while the linkage is Parrot_somefunc(interp,a,b,c) for namespace cleanup Once the STM merge is done, I will enjoy crying "Havoc!" and letting slip the cage cleaners of war. -- Chip Salzenberg <[EMAIL PROTECTED]>

Namespace.get_namespace() vs. optional params

2006-07-17 Thread Chip Salzenberg
ectly the first time, but it's just another thing to do as part of the conversion). Mind you, I'm OK with this, but it's something to be aware of. -- Chip Salzenberg <[EMAIL PROTECTED]>

Re: PDD 23 Exceptions - ready for implementation

2006-07-14 Thread Chip Salzenberg
will come before exception implementaiton. Exceptions are important, but if you can't even find your variables, you're pretty much up the creek. -- Chip Salzenberg <[EMAIL PROTECTED]>

"_group" in library name (was Re: r13272 - in trunk: compilers/imcc docs/imcc src)

2006-07-12 Thread Chip Salzenberg
ring inside the library name. Urque, that's really not OK even in the short term. Could you alter it to use an adverb: .loadlib 'perl6_group' :hll please? PS: yes, I am planning to standardize on lower case for pir directives PPS: yes, I am planning to let the upper-case &q

Re: Creating a New Object (was Re: [TODO] Implement .loadlib pragma in IMCC)

2006-07-12 Thread Chip Salzenberg
On Wed, Jul 12, 2006 at 12:15:07PM -0700, Chip Salzenberg wrote: > >- If another HLL wants to create a Perl6Str, how does it do it? > >- If another HLL wants to create a subclass of Perl6Str...? I just realized that I misinterpreted these questions. I thought that the first

Re: Creating a New Object (was Re: [TODO] Implement .loadlib pragma in IMCC)

2006-07-12 Thread Chip Salzenberg
amespaces at all, leaving it up to the user to give it a name ... if any. Yes, Virginia, there are anonymous classes. :-) So it might look like: .HLL "evillang" .sub foo $P0 = newclass ... set_hll_global ['Perl6Str'], $P0 # Not a Perl 6 string, but an incredible simulation ... -- Chip Salzenberg <[EMAIL PROTECTED]>

Re: [perl #39777] Macro array considered lame

2006-07-12 Thread Chip Salzenberg
On Mon, Jul 10, 2006 at 12:09:08AM -0500, Vishal Soni wrote: > -#define N_MACROS 4096 > +#define N_MACROS 8192 Thanks, applied. But we can all see where this is going. Will no one rid me of this troublesome fixed-size array for macros? -- Chip Salzenberg <[EMAIL PROTECTED]>

Re: [perl #39792] [TODO] Deprecate :immediate in favour of .loadlib and .const

2006-07-11 Thread Chip Salzenberg
x27;s BEGIN; it's not intended to be a tool for implementing BEGIN when compiling Perl. [*] Just what it _is_ intended for is an open question. I think the user base will answer it, if we let them, in time. -- Chip Salzenberg <[EMAIL PROTECTED]>

Re: [perl #39792] [TODO] Deprecate :immediate in favour of .loadlib and .const

2006-07-11 Thread Chip Salzenberg
npredictable is to make a null statement, because in practice, all computation is unpredictable. -- Chip Salzenberg <[EMAIL PROTECTED]>

Re: [perl #39792] [TODO] Deprecate :immediate in favour of .loadlib and .const

2006-07-11 Thread Chip Salzenberg
d to start and stop a new Parrot VM each time, well, that's no different in principle from a programmer typing "make distclean" to remove all the intermediate products of autoconf or op2c.pl or whatever. -- Chip Salzenberg <[EMAIL PROTECTED]>

Re: Stealing base

2006-07-10 Thread Chip Salzenberg
ou delay the final choice utnil you write the PDD, then to with whatever opcode name looks best in the =item that precedes its description. :-) -- Chip Salzenberg <[EMAIL PROTECTED]>

Re: HLL root globals and empty keys (was Re: test of get_namespace opcode)

2006-07-10 Thread Chip Salzenberg
On Mon, Jul 10, 2006 at 07:22:21PM -0700, Allison Randal wrote: > Chip Salzenberg wrote: > > I think that "hll" is the best I can think of, and given the existing > > ".HLL" directive, its meaning is immediately clear: > > I like that. Great! > >

Re: Re: HLL root globals and empty keys (was Re: test of get_namespace opcode)

2006-07-10 Thread Chip Salzenberg
d_global 'x' -> $P0 = get_global 'x' $P1 = find_global ['ns'],'x' -> $P0 = get_hll_global ['ns'],'x' -- Chip Salzenberg <[EMAIL PROTECTED]>

Re: [perl #39778] Segfault when using a Namespace with an Iterator

2006-07-10 Thread Chip Salzenberg
space so that Parrot no longer requires a class object and its namespace object to have the same name. I'm going to create a bug for this plan and then connect that bug to this. -- Chip Salzenberg <[EMAIL PROTECTED]>

Re: OSCON hackathon

2006-07-10 Thread Chip Salzenberg
rials can > perhaps continue hacking activities on those days...? I think it'd be great to maintain a hackathon designated location for those who are between tutorials, or who like me just show up during tutorial days for the hell of it. :-) -- Chip Salzenberg <[EMAIL PROTECTED]>

Re: HLL root globals and empty keys (was Re: test of get_namespace opcode)

2006-07-10 Thread Chip Salzenberg
On Mon, Jul 10, 2006 at 03:23:56PM -0500, Patrick R. Michaud wrote: > On Sat, Jul 08, 2006 at 01:57:58PM -0700, Chip Salzenberg wrote: > > Relative is the usual apposite to absolute, but we have a three-way > > logic here, so appositives don't really work. I think that "h

Re: The handled op forces resumption?

2006-07-09 Thread Chip Salzenberg
27;t handle it" just return So in short I think C should go back to merely clearing the "exception in progress" but not transfer control. -- Chip Salzenberg <[EMAIL PROTECTED]>

Re: A PDD for dynamic-wind?

2006-07-08 Thread Chip Salzenberg
sily understood and, perhaps, adopted. PS: All of this is about foreground projects. Background and bug fixes always go on. -- Chip Salzenberg <[EMAIL PROTECTED]>

Re: HLL root globals and empty keys (was Re: test of get_namespace opcode)

2006-07-08 Thread Chip Salzenberg
when they were found. (particle++ for the finding) } On Fri, Jul 07, 2006 at 12:46:35AM -0700, Allison Randal wrote: > Chip Salzenberg wrote: > >Well, I see a lot to like about this, but (and you knew there was a "but" > >("but" that's my job now :-))), i

Re: pdd21 vs. find_global

2006-07-08 Thread Chip Salzenberg
On Sat, Jul 01, 2006 at 10:37:59PM -0500, Allison Randal wrote: > I'm more inclined to say find_global just shouldn't accept a namespace PMC > as an argument. For those who aren't reading the subversion logs: 1. Why aren't you? :-) 2. I've done this -- Chip Salzenberg <[EMAIL PROTECTED]>

Re: HLL root globals and empty keys (was Re: test of get_namespace opcode)

2006-07-08 Thread Chip Salzenberg
r its parent, and I don't want to do that. Given the presence of namespace aliasing, a namespace isn't guaranteed to have a single parent, or that that parent will be the one it was, er, born with. The compiler knows the full name and it's easy enough for the compiler to strip the last element off the namespace path. -- Chip Salzenberg <[EMAIL PROTECTED]>

I'm pre-hackathoning at OSCON, not post-hackathoning

2006-07-07 Thread Chip Salzenberg
I'm unable to hang around Portland after Friday afternoon, I'm sorry to report, so Saturday hackathoning will miss me. However, I will be arriving a day _early_ so I'll be in Portland all day Sunday. I understood Patrick to be in a similar situation, so he might be there Sunda

[perl #39552] Segfault on FreeBSD during make

2006-07-07 Thread Chip Salzenberg via RT
Is this bug still reproducible this even after removing everything Parrot-related from /usr/local? (Also /usr/bin and /usr/lib if you happen to have installed e.g. Debian's parrot packages.)

Re: PGE and TGE vs. .namespace

2006-07-06 Thread Chip Salzenberg
On Thu, Jul 06, 2006 at 10:01:39PM -0700, Chip Salzenberg wrote: > On Thu, Jul 06, 2006 at 05:22:47PM -0700, Allison Randal wrote: > > jerry gay wrote: > > >On 7/6/06, Allison Randal <[EMAIL PROTECTED]> wrote: > > > > > >meanwhile, back at the ranch

Re: PGE and TGE vs. .namespace

2006-07-06 Thread Chip Salzenberg
PGE test(s)? Oddly enough, no. I actually made it worse, to my great surprise. Still hacking tho... -- Chip Salzenberg <[EMAIL PROTECTED]>

Re: PGE and TGE vs. .namespace

2006-07-06 Thread Chip Salzenberg
On Thu, Jul 06, 2006 at 04:44:35PM -0700, jerry gay wrote: > On 7/6/06, Allison Randal <[EMAIL PROTECTED]> wrote: > >Chip Salzenberg wrote: > >> The below patches are my guess as to how to fix PGE and TGE for the > >recent > >> change in .namespace. (That i

Re: HLL root globals and empty keys (was Re: test of get_namespace opcode)

2006-07-06 Thread Chip Salzenberg
$P0 = get_cur_global ['Bar'], 'x' # ['perl5';'Foo';'Bar';'x'] $P0 = get_global 'x' # ['perl5';'x'] $P0 = get_global ['Corge'], 'x' # ['perl5';'Corge';'x'] $P0 = get_abs_global 'x' # ['x'] $P0 = get_abs_global ['parrot'], 'x' # ['parrot';'x'] (If there is no Null, substitute a null PMC register.) -- Chip Salzenberg <[EMAIL PROTECTED]>

Re: HLL root globals and empty keys (was Re: test of get_namespace opcode)

2006-07-06 Thread Chip Salzenberg
m conformable with using interpinfo to get the global root. And of course the current namespace maps onto the Unix working dir for me. -- Chip Salzenberg <[EMAIL PROTECTED]>

Re: [perl #39743] [PATCH] change perl6-internals to parrot-porters in docs

2006-07-06 Thread Chip Salzenberg
I wish I saw it used more. -- Chip Salzenberg <[EMAIL PROTECTED]>

PGE and TGE vs. .namespace

2006-07-06 Thread Chip Salzenberg
mar == '' goto pir_emit +nsformat = ".namespace [ '%0' ]" + pir_emit: code = new 'PGE::CodeString' -code.emit(".namespace [ '%0' ]", grammar) +code.emit(nsformat, grammar) $P0 = exp.root_pir(adverbs :flat :named) code .= $P0 if target != 'PIR' goto bytecode -- Chip Salzenberg <[EMAIL PROTECTED]>

.namespace [''] in TGE

2006-07-06 Thread Chip Salzenberg
ot;' ]" + no_type: +code .= "\n\n" code .= ".sub '__onload' :load\n" code .= "load_bytecode 'TGE.pbc'\n" code .= "$I0 = find_type '" -- Chip Salzenberg <[EMAIL PROTECTED]>

Re: HLL root globals and empty keys (was Re: test of get_namespace opcode)

2006-07-06 Thread Chip Salzenberg
voiding explicit re-coding of a known bit of environmental information, as in "the first floor of this building" rather than "the first floor of 123 main street". > Chip Salzenberg wrote: > >Allison, what do you think of zero-length keys, i.e. having [] construct a >

HLL root globals and empty keys (was Re: test of get_namespace opcode)

2006-07-05 Thread Chip Salzenberg
On Sat, Jul 01, 2006 at 03:04:05PM -0700, Matt Diephouse wrote: > Chip Salzenberg <[EMAIL PROTECTED]> wrote: > > .namespace # no key > >means the HLL root. > > That resolves the other ticket I opened yesterday (good). But I'd > prefer to have C< .namespa

Re: [PATCH] #38627: [TODO] fill Parrot_register_move() with code

2006-07-03 Thread Chip Salzenberg
On Mon, Jul 03, 2006 at 03:39:19PM -0500, Vishal Soni wrote: > On Mon, 2006-07-03 at 13:03 -0700, Chip Salzenberg wrote: > > The use of a fixed constant like MAX_REGISTER doesn't really work; Parrot > > has an unbounded (if not infinite :-)) number of registers [...] > &

Re: [PATCH] #38627: [TODO] fill Parrot_register_move() with code

2006-07-03 Thread Chip Salzenberg
[MAX_REGISTER],unsigned char (*val),int > src , int prev, int depth , reg_move_func mov,Interp *interpreter,void > *info,int temp) > +{ > +int i=0; > +val[src]=1; > +for (i=0;i +{ > +if (a[src][i]>0 ) > +{ > +if (val[i]==1) > +{ > + emit_mov(mov,interpreter,info,prev,0,i,src,temp); > + emit_mov(mov,interpreter,info,prev,depth <= 1,src,prev,temp); > +return 1; > +} > +if (val[i]!=2 ) > +{ > +depth++; > +int > x=reorder_move(a,val,i,src,depth,mov,interpreter,info,temp); > +depth--; > +emit_mov(mov,interpreter,info,prev,x && (depth <= > 1),src,prev,temp); > +return x; > +} > +} > +} > +val[src]=2; > +emit_mov(mov,interpreter,info,prev,0,src,prev,temp); > +return 0; > +} > + > +void emit_mov(reg_move_func mov,Interp *interpreter,void *info,int emit,int > emit_temp,int dest,int src,int temp) > +{ > +if (emit >-1 ) > + { > + if (emit_temp) > + { > + mov(interpreter,dest,temp,info); > + } > + else > + { > + mov(interpreter,dest,src,info); > + } > + } > +} > /* > > =back -- Chip Salzenberg <[EMAIL PROTECTED]>

pdd21 vs. find_global

2006-07-01 Thread Chip Salzenberg
rface, find_global is obsolete. Where you would say $P0 = find_global key_or_array, 'foo' you change to $P99 = get_namespace key_or_array $P0 = $P99['foo'] which also incidentally encourages(!) compilers to cache namespace pointers. -- Chip Salzenberg <[EMAIL PROTECTED]>

Re: Re: test of get_namespace opcode vs. arrays

2006-07-01 Thread Chip Salzenberg
On Sat, Jul 01, 2006 at 01:30:40PM -0700, Matt Diephouse wrote: > Chip Salzenberg <[EMAIL PROTECTED]> wrote: > >The actual bug you've found seems unrelated to the use of the array of > >strings (vs. a key), as substituting the key version: > > $P0 = get_namespace

Re: test of get_namespace opcode vs. arrays

2006-07-01 Thread Chip Salzenberg
ngs (vs. a key), as substituting the key version: $P0 = get_namespace [''] still fails. Debugging in progress. -- Chip Salzenberg <[EMAIL PROTECTED]>

Onward & Upward: New Assignments

2006-07-01 Thread Chip Salzenberg
that I'm going to carry the release cycle burden, he'll have more opportunity to respond to language implementors' issues, making Parrot better for all. Onward & upward! *Squawk*! -- Chip Salzenberg <[EMAIL PROTECTED]>

  1   2   3   4   5   >