Matt Diephouse (via RT) wrote:
$P0 = compreg "PIR"
.return $P0(code)
.end
[EMAIL PROTECTED]:~/parrot$ parrot test.pir
attempt to access code outside of current code segment
[EMAIL PROTECTED]:~/parrot$
This was the cause of some trouble recently for Partcl (although I
di
Chip Salzenberg wrote:
> Audrey, I just committed the below to pdd03 because I think it'll work for
> Pugs. What say?
Say sane. Thanks!
Audrey
signature.asc
Description: OpenPGP digital signature
(NOTE: I invite PIR users to read this msg, and especially item #5, and let
me know whether you'll suffer any breakage when/if Parrot default namespaces
go untyped, i.e. when you're no longer allowed to have a namespace and a
global variable with the same name but distinct. HLL-specific namespaces
Er, it's really early (excuse generator #17). So please ignore this:
On Tue, Mar 14, 2006 at 08:03:02AM -0800, Chip Salzenberg wrote:
> 1. Independent of other issues, you've prompted me to notice that I omitted
> namespaces themselves from the namespace typed interface. Hence the
> typ
On Fri, Mar 10, 2006 at 01:06:10PM +0100, Leopold Toetsch wrote:
> ('::' is the namespace delimiter according to pdd21 and not to be taken
> literally)
Indeed so; but the Perl and C++ usage is so ingrained that people are still
instinctively trying to use it. So, it's time for a bigger hammer.
F
On Tuesday 14 March 2006 08:03, Chip Salzenberg wrote:
> PIR users: If namespace "foo" and global variable "foo" were no longer
> distinct, so you had to rename one or the other in your code, would
> you suffer any breakage in the first place, and if you did, would you
> have a har
On Tue, Mar 14, 2006 at 08:03:02AM -0800, Chip Salzenberg wrote:
> (NOTE: I invite PIR users to read this msg, and especially item #5, and let
> me know whether you'll suffer any breakage when/if Parrot default namespaces
> go untyped, i.e. when you're no longer allowed to have a namespace and a
>
On Mon, Mar 06, 2006 at 03:31:17PM -0800, Allison Randal wrote:
> On Mar 6, 2006, at 4:08, Leopold Toetsch wrote:
> > * C returns a string representing a socket address
> > [Nicholas] "I don't think that this is appropriate. It's IPv4
> >specific."
> >
> >A more general SocketAddr PMC seems
On Tue, Mar 14, 2006 at 12:14:24PM -0800, chromatic wrote:
> On Tuesday 14 March 2006 08:03, Chip Salzenberg wrote:
> > PIR users: If namespace "foo" and global variable "foo" were no longer
> > distinct, so you had to rename one or the other in your code, would
> > you suffer any break
On Sun, Mar 05, 2006 at 07:11:59PM +, Nicholas Clark wrote:
> =item *
>
> C retrieves information about a file on the filesystem. It takes a
> string filename or an integer argument of a UNIX file descriptor, and an
> integer flag for the type of information requested. It returns an
On Tuesday 14 March 2006 14:14, Chip Salzenberg wrote:
> What, you currently use "::" in your namespace names? On purpose? :-)
I've had objects working in my PIR code before even Dan thought they
worked. Once upon a time, that *was* the way to go.
Now get off my lawn!
-- c
On Tue, Mar 14, 2006 at 02:48:03PM -0800, chromatic wrote:
> On Tuesday 14 March 2006 14:14, Chip Salzenberg wrote:
>
> > What, you currently use "::" in your namespace names? On purpose? :-)
>
> I've had objects working in my PIR code before even Dan thought they
> worked. Once upon a time,
On Mar 14, 2006, at 18:33, Chip Salzenberg wrote:
On Fri, Mar 10, 2006 at 01:06:10PM +0100, Leopold Toetsch wrote:
('::' is the namespace delimiter according to pdd21 and not to be
taken
literally)
Indeed so; but the Perl and C++ usage is so ingrained that people are
still
instinctively t
13 matches
Mail list logo
