interpolate in Perl 6 with bare closures, so
say answer = {foo}
wouldn't be so bad.
: The only thing I hate about Perl with required formatting is the silly
: braces. If it's one line and separated by visible whitespace, why is the
: only option available to me the
:
: statement_1
could concatenate multiline statements with e.g. a backslash.
Some say that there are too much operators in Perl(6). I partially
agree. I don't like the implicit type casting forced by the operators
(== int / eq string). That's harder to learn and remember. Harder to
read also.
I really
part of the language from other languages.
Why not do so again by adopting good ideas.
Don't get me wrong, there's nothing bad in writing some critics, but
yours is impossible to realize in Perl 6
Admittedly I'm much too late and I didn't expect applause for my critics
-- but at least I hoped
On 14 May 2007, at 11:51, Thomas Wittek wrote:
I also can't remember that I ever named a variable like a reserved
word or operator. And even if I could, I'd consider it to be bad
style.
How did you know which reserved words and operators were going to be
introduced in the future so you
be extra-syntax for the rare cases (multiline) and not for
the common ones.
Some say that there are too much operators in Perl(6). I partially
agree.
That's like saying there are too many function calls in Scheme. Perl's an
operator-oriented language!
And it should be. I really like
Andy Armstrong schrieb:
On 14 May 2007, at 11:51, Thomas Wittek wrote:
I also can't remember that I ever named a variable like a reserved
word or operator. And even if I could, I'd consider it to be bad style.
How did you know which reserved words and operators were going to be
introduced in
On 14 May 2007, at 12:31, Thomas Wittek wrote:
How did C, C#, Java, Ruby, Python, Lua, JavaScript, Visual Basic,
etc. know?
They didn't.
If there is a new release, you always have to check if your code
still runs.
I think that may be the point I'm making.
--
Andy Armstrong, hexten.net
herbert breunung schrieb:
please make a decision for you to program in a language [..]
[..] try python. [..]
Oh, just because I think that they've some smart design decisions?
Why not steal them?
BTW: Why do so much people say go away if you don't like it instead of
being open for ideas and
I'm so tired of hearing how unreadable Perl is. It's specious. But
if so many people think it... Uh-uh. Instinctive reactions can be
both universal and incorrect...and I think that's what this is. At
least, among those who have even bothered to look into Perl instead of
just repeating FUD.
herbert breunung schrieb:
please make a decision for you to program in a language [..]
[..] try python. [..]
Oh, just because I think that they've some smart design decisions?
Why not steal them?
BTW: Why do so much people say go away if you don't like it instead of
being open for
Andy Armstrong schrieb:
On 14 May 2007, at 12:31, Thomas Wittek wrote:
How did C, C#, Java, Ruby, Python, Lua, JavaScript, Visual Basic, etc.
know?
They didn't.
If there is a new release, you always have to check if your code still
runs.
I think that may be the point I'm making.
Your
On Mon, May 14, 2007 at 02:36:10PM +0200, Thomas Wittek wrote:
Andy Armstrong schrieb:
On 14 May 2007, at 12:31, Thomas Wittek wrote:
How did C, C#, Java, Ruby, Python, Lua, JavaScript, Visual Basic, etc.
know?
They didn't.
If there is a new release, you always have to check if your code
.
To get away from that image, it's neccessary to do some radical changes
I think.
I agree. You need less ignorant colleagues. I'm not sure Perl 6 can fix
that.
By the way, I'm still waiting to meet your cadre of Dylan hackers.
-- c
On Monday 14 May 2007 04:35:19 Thomas Wittek wrote:
BTW: Why do so much people say go away if you don't like it instead of
being open for ideas and discussing them from a neutral point of view?
Perhaps you're not a native English speaker, but running into the room and
saying Perl 6 doesn't
has stolen the largest part of the language from other languages.
Why not do so again by adopting good ideas.
because, as was pointed out earlier, huge changes
a) delay implementation significantly and
b) change the character of the language too heavily. We want Perl 6 to
be Perl still.
Don't
that it was wrong indeed.
Moritz
--
Moritz Lenz
http://moritz.faui2k3.org/ | http://perl-6.de/
signature.asc
Description: OpenPGP digital signature
On Mon, 14 May 2007 12:51:53 +0200
Thomas Wittek [EMAIL PROTECTED] wrote:
Reason? I still haven't seen a good justification for sigils.
This may not qualify as a good justification, but it is one I've
discussed with others and rings true for many. Take a look at
actual code written
On 5/14/07, John Macdonald [EMAIL PROTECTED] wrote:
Removing the sigil
on a function call (it used to always be written sub(args...))
did, I think, lead to the difficulty in perl5 where it became
difficult to add new keyword operators to the language - because
they could conflict with
. There are far more cases of
single line statements than multiline statements. So you would save
quite some characters, when the semicolon would be optional and you
could concatenate multiline statements with e.g. a backslash.
Some say that there are too much operators in Perl(6). I partially
agree
variable we might create.
The fact that function don't need a sigil any more and it is even
AFAIK discouraged to be used makes *this* argument mute.
Thought this thread might not be the best place to ask this
I'd be glad to read some explanation about this.
In Perl 6, the sigil is used
Thomas Wittek skribis 2007-05-14 0:42 (+0200):
excessive use of special characters (/\W/).
This seems to be I don't like regexes. Ignoring for now that Perl 6
regexes will be more verbose and thus easier to read for someone without
much prior exposure to them, what would you suggest
On Mon, May 14, 2007 at 02:21:47PM -0400, Ryan Richter wrote:
: In Perl 6, the sigil is used to distinguish between
:
: foo bar
:
: which calls bar and passes the return value to foo, and
:
: foo bar
:
: which passes bar as a Code object to foo.
In other words, the sigil is consistently
Frank Wiles schrieb:
Take a look at
actual code written in other languages and you'll find many variable
names that end in things like _ary, _array, _dict, _list, etc.
Actually I've not seen that often. Where I've seen it frequently is in
Visual Basic and Delphi/Pascal.
I hated it too.
But I
of statements,
though
almost no one pronounces them.
Oh, I thought Perl was a programming language. My fault.
Apples and oranges.
Most modern scripting languages don't need the semicolons. I think
there's no plausible reason for them.
I agree. You need less ignorant colleagues. I'm not sure Perl 6 can
At 11:43 -0700 5/14/07, Larry Wall wrote:
In other words, the sigil is consistently a noun marker in Perl 6, even when a
sigil is used on a verb.
It would seem to me that a preprocessor, written in perl of course, could
easily respond to DIMENSION noun AS double statements or whatever you like
is not a variable.
| When you have update(delete_random), where both update and
| delete_random are functions, does this pass the function delete_random
| to update, or does it first delete something, and then pass the
| resulting value to update?
The Perl 6 Way:
update(delete_random) passes the function
Thomas Wittek skribis 2007-05-14 22:31 (+0200):
$.but! (*adding$ %*characters _+that^# $might) @#not_ !#be()
!necessary_ *#$doesn't! *(make) [EMAIL PROTECTED] =_easier
Those characters are meaningless. The many symbols in Perl 6 have very
distinct meanings, which makes them very powerful tools
Good examples. Now could you provide some to explain to me why it's
important to distinguish between '$', '@', '%', and ''? I ask
because I've seen a lot of object-based code that has said stuff like
'$container{$key}'; it seems that there's an assumption that $foo can
be used as a list, a
On 5/14/07, Jonathan Lang [EMAIL PROTECTED] wrote:
Good examples. Now could you provide some to explain to me why it's
important to distinguish between '$', '@', '%', and ''? I ask
because I've seen a lot of object-based code that has said stuff like
'$container{$key}';
Well,
trump custom. Also, of course, remember that Larry's a pretty
smart guy, particularly in the linguistics field. There are more people
working in perl than work in Esperanto.
I agree. You need less ignorant colleagues. I'm not sure Perl 6 can fix
that.
I don't think that it's a point
Juerd Waalboer schrieb:
Thomas Wittek skribis 2007-05-14 0:42 (+0200):
excessive use of special characters (/\W/).
This seems to be I don't like regexes. Ignoring for now that Perl 6
regexes will be more verbose and thus easier to read for someone without
much prior exposure to them, what
Jonathan Lang skribis 2007-05-14 14:52 (-0700):
Good examples. Now could you provide some to explain to me why it's
important to distinguish between '$', '@', '%', and ''?
It's useful code self documentation, but not very important, in my
opinion.
If you have sigils, it makes sense to have
Austin Hastings:
A similar trade-off exists with the statement terminating semicolon. In
this case, it involves the number of statements per line:
A language that terminates statements can ignore whitespace, allowing
multiple statements per line and statements that span multiple lines.
Thomas Wittek skribis 2007-05-15 1:03 (+0200):
On the other hand, the overall structure of a program is often more
obvious, exactly because so much more fits in one screenful.
My suggestions won't have an impact on the expressiveness of Perl.
Not so.
Consider /@foo/, which is an
that does Hash should be able to call the above method.
And unless I've missed something, there's nothing in perl 6 that
insists that an object that does Hash must be assigned to a variable
that uses the '%' sigil; the '$' sigil seems to work equally well.
i.e., I've seen code to the effect
. Really.
Reason? I still haven't seen a good justification for sigils.
Whether you like it or not, sigils are a part of Perl's personality that
aren't going away any time soon. If you don't like them, then you shouldn't
use perl. All those people claiming that Perl 6 isn't Perl would
. There are far more cases of
single line statements than multiline statements. So you would save
quite some characters, when the semicolon would be optional and you
could concatenate multiline statements with e.g. a backslash.
Some say that there are too much operators in Perl(6). I partially
agree
get me wrong, there's nothing bad in writing some critics, but
yours is impossible to realize in Perl 6
Admittedly I'm much too late and I didn't expect applause for my critics
-- but at least I hoped to get a discussion based on arguments.
and therefore are it's hard to call it constructive
more cases of
single line statements than multiline statements. So you would save
quite some characters, when the semicolon would be optional and you
could concatenate multiline statements with e.g. a backslash.
Some say that there are too much operators in Perl(6). I partially
agree. I don't like
the python way, feel free to code in python.
Perhaps some day it will be possible to mix them:
use python;
# Write python code here
Don't get me wrong, there's nothing bad in writing some critics, but
yours is impossible to realize in Perl 6, and therefore are it's hard to
call it constructive
that there are too much operators in Perl(6). I partially
agree.
That's like saying there are too many function calls in Scheme. Perl's an
operator-oriented language!
People not only want code that _is_ sexy, but they also want it to
_look_ sexy.
You'll have to find me more than a handful of Dylan
On Thursday 03 May 2007 03:06:43 Andrew Shitov wrote:
What is nedded is a very simple step:
Contributors.
-- c
=HI!
To avoid any uncertainty: the subject is a parody for similar
discussion on perl6-internals@ about Parrot.
=FOREWORD
What I want to say is that after N years of developing Perl 6 we do
not have a practical (P in Perl stands for Practical) tool which can
work in real life.
Even worse: today
We're pleased to announce that we've selected Phil Crow as the recipient of the
second Perl 6 microgrant. Phil is the hacker behind the Java::Swing module
which allows Perl programmers to put a Java Swing GUI on their application
without writing any Java and he'll be using this knowledge
parse the java .h files that that define the JDBC
API,
e.g.,
http://gcc.gnu.org/viewcvs/trunk/libjava/java/sql/Statement.h?revision=120621view=markup
and generate roughly equivalent Perl 6 (roles etc).
I notice that this file (and all of the others I looked at) say at the top:
// DO NOT EDIT
/third_edition/html/grammars.html
and writes a parser in Perl 6 for that grammar.
Writing a Perl 6 grammar to parse BNF should not be too hard.
Writing a 5.10 regular expression to parse BNF shouldn't be too hard either.
Abigail
pgp0QsSS8lU00.pgp
Description: PGP signature
I'm pleased to announce the inaugural Perl 6 Microgrants program.
Best Practical Solutions (my company) has donated USD5,000 to The
Perl Foundation to help support Perl 6 Development. Leon Brocard,
representing The Perl Foundation's grants committee, will work with
me to select proposals
On Wed, Mar 21, 2007 at 11:04:29PM -0400, Jesse Vincent wrote:
I'm pleased to announce the inaugural Perl 6 Microgrants program.
Best Practical Solutions (my company) has donated USD5,000 to The
Perl Foundation to help support Perl 6 Development. Leon Brocard,
representing The Perl
.
So, are there others that would work with me?
Phil
Tim Bunce [EMAIL PROTECTED] wrote:
On Wed, Mar 21, 2007 at 11:04:29PM -0400, Jesse Vincent wrote:
I'm pleased to announce the inaugural Perl 6 Microgrants program.
Best Practical Solutions (my company) has donated USD5,000 to The
Perl
On Thu, Mar 22, 2007 at 01:24:58PM +, Tim Bunce wrote:
Here's a related idea: write a tool that reads BNF grammar, such as
http://java.sun.com/docs/books/jls/third_edition/html/syntax.html
http://java.sun.com/docs/books/jls/third_edition/html/grammars.html
and writes a parser in Perl 6
: Jesse Vincent [EMAIL PROTECTED]
Date: Mar 22, 2007 11:04 AM
Subject: Perl 6 Microgrants. Now accepting proposals.
To: perl6-internals@perl.org, perl6-language@perl.org,
perl6-compiler@perl.org, perl5-porters@perl.org
I'm pleased to announce the inaugural Perl 6 Microgrants program.
Best Practical
# FYI. The note below was originally posted on perl.perl6.users.
# Thought some folks here should also be interested in this.
#
# Background:
#
# http://www.nntp.perl.org/group/perl.perl6.internals/34764
# Announcing the Perl 6 and Parrot wiki workspaces
#
# http://www.nntp.perl.org/group
perl.org).
Copyright and License
* (c) 2006 under the same (always latest) license(s) used by
the Perl 6 /src branch of the Pugs trunk.
* See http://svn.perl.org/perl6/pugs/trunk/README for the latest details.
* See the GPL-2, Artistic-2.0b5, and MIT files in
http://svn.perl.org
AT == Audrey Tang [EMAIL PROTECTED] writes:
AT Indeed. So instead of having the implementions define the language,
AT this time around the specs, and tests, and API documentations, need
AT to be adhered closely by implementors, which is why we're all talking
AT together in #perl6 in the
Sage La Torra writes:
interpolative context ment the perl 5 side, where the double quotes
should cause interpolation.
Yes, but not for entire hashes; the percent character isn't special in
Perl 5 double-quoted strings, as Aaron said:
On 6/6/06, Aaron Crane [EMAIL PROTECTED] wrote:
Sage
Just an update:
I've started coding (in haskell, to be used with Pugs). I've got file input,
I've got a data structure for the AST, now I just have to make them play
nicely together. I'll start implementing translations soon, so any other
corrections would be appreciated.
Thanks to everyone
Sage La Torra writes:
http://infohost.nmt.edu/~slatorra/conversionstageone.txt
You say this:
-Hash in interprative context: %hash - %hash{} (also @{[...]} -
{...})
Hashes don't interpolate in Perl 5, so that's not an issue (unless I'm
misunderstanding what you meant). But using {...}
interpolative context ment the perl 5 side, where the double quotes should
cause interpolation. Maybe not the best phrase to identify it, now that you
mention it.
Sage
On 6/6/06, Aaron Crane [EMAIL PROTECTED] wrote:
Sage La Torra writes:
http://infohost.nmt.edu/~slatorra
Hello all,
I'm the student picking up on the translation work lwall started. Since the
perl 5 parser is more or less complete, I've headed straight to the
translation work. I'm going to be taking on the translations a few at a
time, starting with the easiest translations and moving to the more
Sage La Torra schreef:
http://infohost.nmt.edu/~slatorra/conversionstageone.txt
Any advice/comments/criticism on the document and even ideas on
implementation would be greatly appreciated.
I think that
split('\s+') - split(/\s+/)
should be
split('\s+') - .split(/\s+/)
--
Groet,
Sage La Torra [EMAIL PROTECTED] wrote:
I've got a design document detailing the first few translations I'll be
handling, and I'd greatly appreciate feedback and advice.
I may be off base here, or in the alternate pointing out a corner case
that's of little significance, but:
-Compound
of the places the translator guessed. But unlimited tying is
one of the problems with Perl 5 that Perl 6 is trying to control, so it's
sort of natural that the translator would run into this here and there.
Another minor difference is that or guarantees an ordered
short-circuit while | may short-circuit
Sage La Torra wrote:
Hello all,
I'm the student picking up on the translation work lwall started. Since the
perl 5 parser is more or less complete, I've headed straight to the
translation work. I'm going to be taking on the translations a few at a
time, starting with the easiest translations and
On 6/2/06, Paul Hodges [EMAIL PROTECTED] wrote:
Though if that works, you could squish this example even more, to
class QueueRunner {
our sub process_queue(Code @jobs_in) {
map { async { _() } } @jobs_in;
}
}# end QueueRunner
# Elsewhere...
my @answer
--- Ashley Winters [EMAIL PROTECTED] wrote:
On 6/2/06, Paul Hodges [EMAIL PROTECTED] wrote:
my @answer = map { async { _() } } @jobs;
That still seems too explicit. I thought we had hyperoperators to
implictly parallelize for us:
my @answer = @jobs.»();
Which would run them
On Sat, Jun 03, 2006 at 03:51:45PM -0700, Paul Hodges wrote:
: --- Ashley Winters [EMAIL PROTECTED] wrote:
: On 6/2/06, Paul Hodges [EMAIL PROTECTED] wrote:
:
:my @answer = map { async { _() } } @jobs;
:
: That still seems too explicit. I thought we had hyperoperators to
: implictly
--- Larry Wall [EMAIL PROTECTED] wrote:
On Sat, Jun 03, 2006 at 03:51:45PM -0700, Paul Hodges wrote:
: { no threads;
:print @_.»();
: }
It seems a bit odd to use a construct for its syntactic sugar value
but take away its semantics...
If you just need ordering, this (or
James Mastros wrote:
I don't like the name synchronized -- it implies that multiple
things are happening at the same time, as in synchronized swiming,
which is exactly the opposite of what should be implied.
Serialized would be a nice name, except it implies serializing
to a
--- John Drago [EMAIL PROTECTED] wrote:
You mean is parallel as a synonym for is async?
I think is parallel denotes something as usable by multiple threads
simultaneously, in parallel.
is serial would denote that only one thread can use the $thing at a
time, exclusively.
Are you saying
Bar.Baz
6 Bar.Baz
4 Foo.Qux
7 Bar.Baz
8 Bar.Baz
5 Foo.Qux
9 Bar.Baz
10 Bar.Baz
(Now the first thread would be done with $foo, so the second thread could use
it.)
6 Foo.Qux
7 Foo.Qux
8 Foo.Qux
9 Foo.Qux
10 Foo.Qux
---
Regards,
John Drago
--- John Drago [EMAIL PROTECTED] wrote:
. . .
class QueueRunner {
our sub process_queue(Code @jobs_in) {
my @ans is serial;
@ans.push map { async { _() } } @jobs_in;
@ans;
}
}
my @answer = QueueRunner.process_job_queue( @jobs );
Actually I think you did
I asked this via the Google Groups interface a few weeks ago, but I'm not sure
if it made it here.
I am asking again in case the question never made it onto the list.
Has the syntax for synchronized/threaded @things been worked out?
For example:
class Foo is synchronized {
...
}
our method
On Tue, May 30, 2006 at 03:41:06PM -0600, John Drago wrote:
I asked this via the Google Groups interface a few weeks ago, but I'm not
sure if it made it here.
I am asking again in case the question never made it onto the list.
Has the syntax for synchronized/threaded @things been worked
James Mastros skribis 2006-05-31 12:03 (+0100):
I don't like the name synchronized -- it implies that multiple things are
happening at the same time, as in synchronized swiming, which is exactly the
opposite of what should be implied. Serialized would be a nice name,
except it implies
How about one of these?
==
class Baz {
has $.a is restricted;
has $.b is controlled;
has $.c is unique;
has $.d is shared;
has $.e is queued;
has $.f is token;
...
}
--- John Drago [EMAIL PROTECTED] wrote:
I asked this via the Google Groups interface
:[EMAIL PROTECTED]
Sent: Wednesday, May 31, 2006 9:43 AM
To: perl6-language@perl.org
Subject: Re: Synchronized / Thread syntax in Perl 6
On Tue, May 30, 2006 at 03:41:06PM -0600, John Drago wrote:
class Foo is synchronized {
...
}
our method Bar is synchronized {
...
}
class
James Mastros wrote:
I don't like the name synchronized -- it implies that multiple things are
happening at the same time, as in synchronized swiming, which is exactly the
opposite of what should be implied. Serialized would be a nice name,
except it implies serializing to a serial format,
--- John Drago [EMAIL PROTECTED] wrote:
James Mastros wrote:
I don't like the name synchronized -- it implies that multiple
things are happening at the same time, as in synchronized swiming,
which is exactly the opposite of what should be implied.
Serialized would be a nice name, except
The (oh so very cool) idea of implementing the perl 6 wiki IN perl 6
(eventually) is a powerful argument. I also concede that control
issues mean we don't want the official wiki to be on wikipedia. Kwiki
is already a perl-based wiki, but I have no experience using it. We
don't have to put perl 6
Please, for proper threading, don't reply to multiple messages at once.
Conrad Schneiker skribis 2006-05-25 1:46 (-0700):
Juerd wrote:
Feather, the semi-public, semi-private, Perl 6 development server, is
available to host a Perl 6 wiki.
The hostname www.perl6.nl is deliberately kept
From: Michael Mathews
I for one, think a Perl6-users wiki would be extremely useful, I'm
just not sure why a site that distinguishes itself as a portal for
the Australian and New Zealand Perl community makes the most sense
I was only thinking of the availability of an existing Perl 6 Wiki
I was googling around, looking for the most suitable Perl Wiki for a
possible addition of a Perl 6 section, and happened across this site:
Perl 6 Wiki: (http://perl.net.au/wiki/Perl_6).
Their posted policies, FAQ, and (http://perl.net.au/wiki/PerlNet:About),
seem to be very favorably
Conrad Schneiker skribis 2006-05-23 0:42 (-0700):
Perl 6 Wiki: (http://perl.net.au/wiki/Perl_6).
That's a nice page, and Mediawiki is a nice wiki. But I'd really prefer
a wiki written in Perl 6, because it's about time we started to show
off. Serving important information with PHP
on an interstate training
assignment until the end of the week, and I'm scrounging net access where I
can.
Conrad Schneiker wrote:
[snip]
Their posted policies, FAQ, and (http://perl.net.au/wiki/PerlNet:About),
seem to be very favorably inclined to serving the purposes of recent Perl
6
Wiki
to be very favorably inclined to serving the purposes of recent Perl 6
Wiki proposals made on comp.perl6.lang and comp.perl6.users. (I've cc'd
their contact on this note.)
As one of the PerlNet admins, I'd be delighted if PerlNet was used to assist in
any Perl 6 development, discussions, or other
of the week, and I'm scrounging net access where I
can.
Conrad Schneiker wrote:
[snip]
Their posted policies, FAQ, and (http://perl.net.au/wiki/PerlNet:About),
seem to be very favorably inclined to serving the purposes of recent Perl
6
Wiki proposals made on comp.perl6.lang and comp.perl6.users. (I've
API in Perl 6 using Pugs.
The goal is to maintain the familiar DBI API while radically refactoring
the internals to make best use of Perl 6 and so enable greater
functionality and extensibility. (Likely mentor: Tim Bunce)
Trying to come up with both a new architecture and a new API was too
This note is crossposted to perl.perl6.language; please include
perl.perl6.meta on replies.]
Feedback on the draft FAQ below will be appreciated. TIA.
Anyone have a contact at Google they can ping about getting
Google Groups to start picking up comp.perl6.meta?
= Perl 6 User FAQ
Not entirely related, but:
it would be great if someone wrote usable wiki software (with revision
control support) in Perl 6, and could maintain it so that it keeps up
with Pugs. Because of the current state of Pugs, it will have to be
written in a very simple way.
Especially if it looks great
HaloO,
Darren Duncan wrote:
Long story shortened, if we consider the point in time where an
immutable object's constructor returns as being when the object is
born, then we have no problem. Any type of object is thereby immutable
if it can not be changed after its constructor returns.
My
HaloO,
Larry Wall wrote:
On Fri, Apr 28, 2006 at 04:41:41AM +, Luke Palmer wrote:
: It seems like a hash whose values are the unit type. Does Perl have a
: unit type? I suppose if it doesn't, we could define one:
:
:subtype Unit of Int where 1;
:
: (Assuming that where groks
A couple of questions and suggestions about Perl 6 built-in data
types, following a look at the newest S06 (
http://svn.perl.org/perl6/doc/trunk/design/syn/S06.pod ) ...
1. There doesn't seem to be an immutable bit-string type, so unless
I read something wrong, I propose adding one.
Since
How about Bag, a set container? Alternately what we really want is
just a Hash where the type of the value is defined as 1, so it need
not be stored at all. Then most of the syntax for it just falls out
of Hash syntax, unless you like writing $x ∈ $bag instead of $bag{$x}.
Presumably we
On 4/28/06, Larry Wall [EMAIL PROTECTED] wrote:
How about Bag, a set container? Alternately what we really want is
just a Hash where the type of the value is defined as 1, so it need
not be stored at all. Then most of the syntax for it just falls out
of Hash syntax, unless you like writing $x
On Fri, Apr 28, 2006 at 04:41:41AM +, Luke Palmer wrote:
: It seems like a hash whose values are the unit type. Does Perl have a
: unit type? I suppose if it doesn't, we could define one:
:
:subtype Unit of Int where 1;
:
: (Assuming that where groks whatever when does).
:
: Then your
At 9:07 PM -0700 4/27/06, Mark A. Biggar wrote:
I'm not sure that immutable make any sense as a concept separate from
constant. A truly immutable object can't even be initialized, it has to
be born ex-nilo already with a value.
Well, that depends on your philosophy.
I would argue that,
* Stevan Little ([EMAIL PROTECTED]) [060305 02:49]:
On 3/4/06, Mark Overmeer [EMAIL PROTECTED] wrote:
Could we try to kind-of pre-register name-spaces for perl6 modules?
There is no need to do such a thing, we have the 3 level naming scheme
in Perl 6 now.
Foo-0.0.1-cpan:JRANDOM
I know
Mark Overmeer skribis 2006-03-05 10:44 (+0100):
I know about the naming scheme, but I am not really looking forward
to the two new perl books Perl DBI-(Any)-cpan:TIMB
and Perl DBI-(Any)-mailto:[EMAIL PROTECTED]
I think that's a very good argument for managing namespace
scheme
in Perl 6 now.
Foo-0.0.1-cpan:JRANDOM
I know about the naming scheme, but I am not really looking forward
to the two new perl books Perl DBI-(Any)-cpan:TIMB
and Perl DBI-(Any)-mailto:[EMAIL PROTECTED]
That you have the possibility to work your way out in namespace
Juerd schreef:
hierarchical names make less
and less sense by the day
I don't oversee the field yet, but maybe:
Introduce aliases (or hardlinks, in file-system-speak).
Likely in a separate top branch, such as @alias::.
The @alias-prefix is only necessary when there is a collision.
601 - 700 of 1442 matches
Mail list logo
