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]
it should be possible to use arbitrary expressions for all
other type/meta operations including introspection, modification,
subclassing, etc.
--
Chip Salzenberg [EMAIL PROTECTED]
entry.
There is no confusion as to which object is the class object.
There is no confusion as to what should be looked up where.
As something of a probing attack -- to provoke informative rebuttal -- I'd
like to propose that type objects should do Package. What say?
--
Chip Salzenberg [EMAIL
are correlated with packages should
instead just _do_ Package.
--
Chip Salzenberg [EMAIL PROTECTED]
On Fri, May 19, 2006 at 02:51:55PM -0700, Chip Salzenberg wrote:
On Fri, May 19, 2006 at 12:53:29PM -0700, Larry Wall wrote:
The type of metaobject Foo.meta might be called Class if that's what the
metaobject protocol decides it should be, but Perl the Language doesn't
care. If so
On Thu, May 18, 2006 at 02:52:53PM -0700, Chip Salzenberg wrote:
{ copied to P6L for the use case question below }
Well, that message wasn't, but this one is...
What's the relationship in perl6 between namespaces and classes?
For example, given:
package Foo { sub bar {...} }
class Corge
On Sat, Nov 19, 2005 at 05:46:51AM +0200, Ilmari Vacklin wrote:
I don't much like it - it looks like a mistyped 'shift'.
Is 'filter' too long?
I usually avoid P6L discussions, but:
GNU Make has filter and filter-out, and I've always found the
polarity hard to remember.
I like grep.
--
Chip
. If they
exist and work, he's not going to break them, but he's not going to do
*anything* to specially support them.
--
Chip Salzenberg [EMAIL PROTECTED]
of named parameters to free the caller from the
tyranny of argument order (and vice versa). It seems to me you're
asking for the worst of both worlds.
--
Chip Salzenberg [EMAIL PROTECTED]
want to intermix the positional parameters with named,
there's no need for us to support intermixing positional parameter
*syntax* with named...?
/me relurks
--
Chip Salzenberg [EMAIL PROTECTED]
. But that
bridge was crossed when you allowed earlier parameters to
participate in the calculation of default values for later ones.
At least it doesn't interfere with MMD.
[*] Autrijus introduced me to this construct, so unless the response
is we changed our mind ...
--
Chip Salzenberg
to denote it.
--
Chip Salzenberg [EMAIL PROTECTED]
On Tue, Jun 14, 2005 at 03:43:42PM +0200, TSa (Thomas Sandlaß) wrote:
Chip Salzenberg wrote:
This:
multi sub is_equal(Integer $a, Integer where { $_ == $a } $b: ) { 1 }
hurts. At least as I've been given to understand it[*], is impossible
to implement, because the second parameter's type
} }
say foo().('$x');
I claim that that should print 1. Chip claims it should throw a warning about
because of timely destruction.
More like an error from the eval: '$x: no such variable in scope'.
--
Chip Salzenberg [EMAIL PROTECTED]
of getting the cwd.
[*] Using the fchdir() system call, you can get close, but it takes
three system calls instead of one; and if you have no fchdir(),
you're out of luck. Oh, and it's not thread-safe.
--
Chip Salzenberg- a.k.a. -[EMAIL PROTECTED]
Open Source
According to Michael G Schwern:
On Fri, Apr 15, 2005 at 08:31:57PM -0400, Chip Salzenberg wrote:
There are several methods to determine the current directory.
Perl 6 is going to have to decide on some sort of standard internal getcwd
technique, $CWD or not.
I don't think Perl 6 has to do
docs add to my anxiety.
Sucker punch. :-)
--
Chip Salzenberg- a.k.a. -[EMAIL PROTECTED]
Open Source is not an excuse to write fun code
then leave the actual work to others.
is it?
--
Chip Salzenberg- a.k.a. -[EMAIL PROTECTED]
Open Source is not an excuse to write fun code
then leave the actual work to others.
of another
process.
Oh, the _directory_ is still there. :-)
--
Chip Salzenberg- a.k.a. -[EMAIL PROTECTED]
Open Source is not an excuse to write fun code
then leave the actual work to others.
According to Abhijit Mahabal:
sub f2c (Num $temp doc Temperature in degrees F) {...}
Nce.
--
Chip Salzenberg- a.k.a. -[EMAIL PROTECTED]
Open Source is not an excuse to write fun code
then leave the actual work to others.
)
docConvert degress F to degrees C
{...}
Or would I be forced to spell it doc('stuff') ?
--
Chip Salzenberg- a.k.a. -[EMAIL PROTECTED]
Open Source is not an excuse to write fun code
then leave the actual work to others.
Larry might have passed arguments by read-only
reference in Perl 5 as well, had he found a way to make it fast.
--
Chip Salzenberg- a.k.a. -[EMAIL PROTECTED]
Open Source is not an excuse to write fun code
then leave the actual work to others.
many constraints for you. You can even add your own
constraints with Cwhere BLOCK subtyping. Amaze your enemies!
Confound your friends! Use Perl6::Subs today!
--
Chip Salzenberg- a.k.a. -[EMAIL PROTECTED]
Open Source is not an excuse to write fun code
are not subsets
of Unicode?
If the explanations are you have greatly misunderstood the contents
of Synopsis $foo, I will happily retire to my reading room.
--
Chip Salzenberg- a.k.a. -[EMAIL PROTECTED]
What I cannot create, I do not understand. - Richard Feynman
According to Rod Adams:
Chip Salzenberg wrote:
* As far as I can tell, the choice of spelling an array parameter
CArray @a or CArray $a is entirely cosmetic: both @a and
$a are capable of holding an Array reference. Is there actually
a difference, e.g. in how they handle an undefined
are their precedence(s)?
--
Chip Salzenberg- a.k.a. -[EMAIL PROTECTED]
Open Source is not an excuse to write fun code
then leave the actual work to others.
According to Austin Hastings:
When you consider some of the issues, it's sort of obvious that they're
trying *real* hard not to say, Look the Americans solved this problem
already.
Three words: Second System Effect.
--
Chip Salzenberg - a.k.a. - [EMAIL PROTECTED]
I
will not name,
... and a public relations issue.
Let us not confuse them.
--
Chip Salzenberg - a.k.a. - [EMAIL PROTECTED]
I wanted to play hopscotch with the impenetrable mystery of existence,
but he stepped in a wormhole and had to go in early. // MST3K
According to Michael Lazzaro:
On Tuesday, December 16, 2003, at 04:01 PM, Chip Salzenberg wrote:
... an anecdote ...
... and a public relations issue.
Let us not confuse them.
I'm not sure I understand which part of that is in conflict.
Speed is for users. PR is for non-users.
You want
According to Larry Wall:
If, by the time the entire program is parsed, nobody has said they
want to extend an interface, then the interface can be considered
closed.
What with Ceval STRING and its various wrappers, when can the program
be said to be fully parsed? - anticipating Mu
--
Chip
According to Larry Wall:
On Sat, 5 Oct 2002, Chip Salzenberg wrote:
: I rather like Perl 5's scalar comma operator.
Most of the uses of which are actually in void context [...]
I didn't realize you were distinguishing scalar from void in this, uh,
context. I agree that scalar comma
was forever bugging me in Python (gack).
--
Chip Salzenberg - a.k.a. -[EMAIL PROTECTED]
It furthers one to have somewhere to go.
to write:
$a = (1,)
then I am going on the warpath. That Way Lay Python.
--
Chip Salzenberg - a.k.a. -[EMAIL PROTECTED]
It furthers one to have somewhere to go.
does[1], and I'm sure I don't want that misfeature in Perl.
[1] for tuples in (), that is. lists use []
--
Chip Salzenberg - a.k.a. -[EMAIL PROTECTED]
It furthers one to have somewhere to go.
According to Luke Palmer:
I think to get Perl5 behavioueaur :), you do this:
my @flatL = ( *(1a, 2a), *(1b, 2b) );
Geez, I hope not, because that would imply that in
my @v = ( func() );
that func is called in a scalar context.
--
Chip Salzenberg - a.k.a. -[EMAIL
[]
is a VERY BAD IDEA.
--
Chip Salzenberg - a.k.a. -[EMAIL PROTECTED]
It furthers one to have somewhere to go.
be a
horrible choice for borrowing from Python. Heck, I'd rather Perl take
Python's import than this abomination of punctuation.
--
Chip Salzenberg - a.k.a. -[EMAIL PROTECTED]
It furthers one to have somewhere to go.
to avoid polluting
the non-all-caps namespace ... ?
--
Chip Salzenberg - a.k.a. -[EMAIL PROTECTED]
It furthers one to have somewhere to go.
it.
--
Chip Salzenberg - a.k.a. -[EMAIL PROTECTED]
It furthers one to have somewhere to go.
According to Dan Sugalski:
One pad per block, rather than per sub.
Because, of course, all blocks are subs. Got it.
--
Chip Salzenberg - a.k.a. -[EMAIL PROTECTED]
It furthers one to have somewhere to go.
According to Dan Sugalski:
At 9:50 PM -0400 7/9/02, Chip Salzenberg wrote:
3a. If so, how can one distinguish among the e.g. many Cmy $foo
variables declared within the current function?
One pad per block, rather than per sub.
I just remembered why I thought that woundn't work
above is yes,
in which case this branch of questions is void).
Larry? Damian? Allison? (Chief? McCloud?)
--
Chip Salzenberg - a.k.a. -[EMAIL PROTECTED]
It furthers one to have somewhere to go.
42 matches
Mail list logo
