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 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 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 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 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
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
(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
On Mar 10, 2006, at 17:45, Chip Salzenberg wrote:
Ah, well, I'm sorry to report that (a) was the correct answer; Parrot's
default should be entirely untyped.
Sorry I didn't catch this earlier, but I'm actually on the road today,
so
it's a good thing I caught it now before users could start co
On Fri, Mar 10, 2006 at 05:33:01PM +0100, Leopold Toetsch wrote:
> >a) Parrot's default namespace is untyped (raw). This means that a
> >variable/subroutine can't have the same name as a namespace. This
> >could break existing code.
> >
> >b) Otherwise, Parrot's namespace is (half-)typed, at leas
On Mar 8, 2006, at 14:30, Leopold Toetsch wrote:
2)
Default Namespace
The default namespace PMC will implement Parrot's current
behavior.
The current implementation allows a nested namespace and a variable to
have the same name (via the hack of prepending "\0" to namespace
n
10 matches
Mail list logo
