Account Options

  1. Sign in
The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Google Groups Home
« Groups Home
perl.perl6.internals
+ new post
About this group
Subscribe to this group
This is a Usenet group - learn more
Message from discussion IMCC looking in P3[0] for 1st arg
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
Steve Fink  
View profile  
 More options Oct 26 2003, 12:48 pm
Newsgroups: perl.perl6.internals
From: st...@fink.com (Steve Fink)
Date: Sun, 26 Oct 2003 09:28:09 -0800
Local: Sun, Oct 26 2003 12:28 pm
Subject: Re: [BUG] IMCC looking in P3[0] for 1st arg
Print | View thread | Show original | Report this message | Find messages by this author
On Oct-26, Leopold Toetsch wrote:

> Steve Fink <st...@fink.com> wrote:
> > I am getting a seg fault when doing a very simple subroutine call with
> > IMCC:

> >     .sub _main
> >             newsub $P4, .Sub, _two_of
> >             $P6 = new PerlHash
> >             .pcc_begin prototyped
>                          ^^^^^^^^^^
> >     .pcc_sub _two_of non_prototyped
>                        ^^^^^^^^^^^^^^

> You are stating explicitely conflicting call types. That can't work.
> When you remove "non_prototyped" in the sub, its prepared to be called
> either way and it works.

Doh! Thanks, I definitely should have noticed that.

Although this does bring up another issue -- should parrot really be
seg faulting when it gets a uninitialized (null) PMC? It happens to me
quite often. In a way, the current behavior is rather nice, since the
errors tend to be more obvious. Then again, that's only because all my
test programs die early enough that no incorrect but non-null values
have snuck into my registers yet. Also, I wouldn't expect a VM to fall
flat on its face from something like this.


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Create a group - Google Groups - Google Home - Terms of Service - Privacy Policy
©2013 Google