Jonathan Lang <[EMAIL PROTECTED]> wrote:
> There are a couple of problems: first, a hash's keys are limited to
> strings; a set ought to be able to handle a wider range of data types.
Last time I checked, there was going to be a way to declare a
different data type for the key (which could easily
On Mon, Feb 21, 2005 at 10:32:15PM -0800, Jonathan Lang wrote:
: ...then you've got the notion of Fuzzy Logic Sets, where the key would be
: the prospective element and the value would be the degree of membership.
: For fuzzy sets, hashes seem to be a better fit than junctions, which have
: no obv
On Mon, Feb 21, 2005 at 09:37:02PM -0600, Steve Peters wrote:
: On Mon, Feb 21, 2005 at 11:32:16AM -0800, Larry Wall wrote:
: > On Mon, Feb 21, 2005 at 02:07:10PM +, osfameron wrote:
: > : >In Perl 6, C<< => >> is a fully-fledged anonymous object constructor
--
: > : >like C<[...]> and
Definitions
===
set (n) : A data container that can hold many elements simultaneously.
The order of elements in a set is meaningless. No two elements in a set
may hold the same value.
junction (n) : The combination of several independent values and an
explicit boolean predicate, to form an
On Mon, 21 Feb 2005, Jonathan Lang wrote:
There are a couple of problems: first, a hash's keys are limited to
strings; a set ought to be able to handle a wider range of data types.
Well, if I had learnt something about Perl6 it is that it is no longer
necessarily so.
Michele
--
It's also amazing
Bob Rogers <[EMAIL PROTECTED]> wrote:
>From: Leopold Toetsch <[EMAIL PROTECTED]>
>I'd pass one argument array around. With Cdoing that anyway.
> Well, the example I showed you was a bit contrived. I'm working on
> implementing Common Lisp call/return semantics, where functions often
Rod Adams wrote:
> The purpose of a junction is to allow for performing several tests at a
> given time, with the testing code needing no knowledge of that junctions
> are present. While a junction can represent several values at the same
> time, such notions as "hold" and "contain" should be avoid
Damian Conway skribis 2005-02-22 22:13 (+1100):
> >@x = func($a, [EMAIL PROTECTED]);
> That's:
> @x = »func«($a, @y);
> But, y'know, this one almost convinces me. Especially when you consider:
> sub func ($i, $j, $k) {...}
> @x = func($a, [EMAIL PROTECTED], @z);
Naievely, I'd ex
Juerd wrote:
Naievely, I'd expect
my @a = @b = 1..3;
»foo«(@a, @b)
to result in
foo(@a[0], @b[0]),
foo(@a[1], @b[1]),
foo(@a[2], @b[2]);
but
foo([EMAIL PROTECTED], [EMAIL PROTECTED])
with the same arrays in
foo(@a[0], @b[0]),
foo(@a[0], @b[1]),
foo(@a[0], @b[2]),
Autrijus wrote:
Personally, I think the only reasonable way of resolving this is to
assume (as in the last paragraph above) that function calls in these
kinds of indeterminate contexts are always in list context.
So, even if the clash is Num vs Str context, we still run it
under List context? Or i
On Tue, Feb 22, 2005 at 10:38:04PM +1100, Damian Conway wrote:
> >So, even if the clash is Num vs Str context, we still run it
> >under List context? Or is it their common ancestor, "Scalar"?
>
> Yes. When I said "indeterminate contexts" I meant List vs Scalar. After
> all, the whole point of mu
I had this silly idea, to try to add %ENV to pugs. That would be an
interesting exercise. So I can write CGI scripts. Maybe. But I don't
know what's the Right way to do it in Perl 6. Any hints ?
--
#!/usr/bin/pugs
say "Just another Pugs hacker";
Hi all,
I was hoping I had a bit more time tonight to work on tests, but house-hacking
projects took precedence. Attached is a patch to t/op/pair.t to add some
additional tests to make sure values of numbers and pairs can be handled as
well as using a pair as a key for a pair.
The test script a
jn Tue, Feb 22, 2005 at 10:54:26AM -, Rafael Garcia-Suarez wrote:
> I had this silly idea, to try to add %ENV to pugs. That would be an
> interesting exercise. So I can write CGI scripts. Maybe. But I don't
> know what's the Right way to do it in Perl 6. Any hints ?
In Perl6 I think you do it
On Tue, Feb 22, 2005 at 08:35:49PM +0800, Autrijus Tang wrote:
> jn Tue, Feb 22, 2005 at 10:54:26AM -, Rafael Garcia-Suarez wrote:
> > I had this silly idea, to try to add %ENV to pugs. That would be an
> > interesting exercise. So I can write CGI scripts. Maybe. But I don't
> > know what's the
On Tue, Feb 22, 2005 at 06:51:24AM -0600, Patrick R. Michaud wrote:
> This might initially work for read-only access/testing, but in
> the long run I suspect that %*ENV will be tied directly to the
> C putenv/getenv calls or their Parrot/other equivalents.
> Assigning to %*ENV should change the e
On Mon, Feb 21, 2005 at 11:05:34PM -0600, Steve Peters wrote:
> I was hoping I had a bit more time tonight to work on tests, but house-hacking
> projects took precedence. Attached is a patch to t/op/pair.t to add some
> additional tests to make sure values of numbers and pairs can be handled as
>
On Tue, Feb 22, 2005 at 12:20:35AM -0800, Larry Wall wrote:
> That seems right to me. Or at least right associative. :-)
>
> In any event, right associativity seems more useful in this case.
Okay, implemented as such.
Of the "non-chaining binaries" in S06:
=> but does cmp <=> .. ^.. ..^ ^
Damian Conway wrote:
>@s = 'item' _ [EMAIL PROTECTED];
That's:
@s = 'item »_« @x;
(just checking that my unerstanding is correct, don't want to be
nitpicking :-)
assuming that you meant to prepend the string "item" to each element of
@x, isn't that:
@s = 'item' »~« @x;
?
furthe
Autrijus Tang wrote:
> jn Tue, Feb 22, 2005 at 10:54:26AM -, Rafael Garcia-Suarez wrote:
> > I had this silly idea, to try to add %ENV to pugs. That would be an
> > interesting exercise. So I can write CGI scripts. Maybe. But I don't
> > know what's the Right way to do it in Perl 6. Any hints ?
On Tue, 22 Feb 2005, Larry Wall wrote:
On Mon, Feb 21, 2005 at 10:32:15PM -0800, Jonathan Lang wrote:
: ...then you've got the notion of Fuzzy Logic Sets, where the key would be
[snip]
But using values for degree of membership is an interesting idea.
On the other hand, if we ever have numeric datat
On Tue, Feb 22, 2005 at 09:07:27PM +0800, Autrijus Tang wrote:
: On Tue, Feb 22, 2005 at 12:20:35AM -0800, Larry Wall wrote:
: > That seems right to me. Or at least right associative. :-)
: >
: > In any event, right associativity seems more useful in this case.
:
: Okay, implemented as such.
:
On Tue, Feb 22, 2005 at 04:17:53PM +0100, Rafael Garcia-Suarez wrote:
> Here's a patch to add this. It's heavily cargo-culted, I need to read
> some docs about haskell some day. As I wasn't able to get FiniteMaps to
> work I implemented my own kludgy function to flatten pairs for the hash.
> Also I
Juerd writes:
> Damian Conway skribis 2005-02-22 22:13 (+1100):
> > >@x = func($a, [EMAIL PROTECTED]);
> > That's:
> > @x = ÂfuncÂ($a, @y);
> > But, y'know, this one almost convinces me. Especially when you consider:
> > sub func ($i, $j, $k) {...}
> > @x = func($a, [EMAIL PROTEC
Some time ago on perl6-documentation (when it existed) we decided that
octals would now be represented as 0o777 and, in strings, \o777. Should
0777 and, in particular, \777 come with warnings? What, exactly, does
\777 mean in a string?
Luke
Damian Conway wrote:
Rod Adams wrote:
> The purpose of a junction is to allow for performing several tests at a
> given time, with the testing code needing no knowledge of that
junctions
> are present. While a junction can represent several values at the same
> time, such notions as "hold" and "co
Luke Palmer skribis 2005-02-22 11:40 (-0700):
> Some time ago on perl6-documentation (when it existed) we decided that
> octals would now be represented as 0o777 and, in strings, \o777. Should
> 0777 and, in particular, \777 come with warnings? What, exactly, does
> \777 mean in a string?
And fo
On Tue, Feb 22, 2005 at 11:40:23AM -0700, Luke Palmer wrote:
: Some time ago on perl6-documentation (when it existed) we decided that
: octals would now be represented as 0o777 and, in strings, \o777. Should
: 0777 and, in particular, \777 come with warnings? What, exactly, does
: \777 mean in a
> "J" == Juerd <[EMAIL PROTECTED]> writes:
J> And for symmetry, can we get 0d and \d for decimal, for those cases
J> where you want to be explicit?
in a regex \d is a digit, so that isn't a good idea. it would be better
to require \0d. the others also need a base designator character so
Uri Guttman skribis 2005-02-22 14:41 (-0500):
> in a regex \d is a digit, so that isn't a good idea
In a rule, whitespace is a very good disambiguator.
> it would be better to require \0d.
I think nullbyte-d is rather likely to occur.
> why would we need 0d123 as a literal?
Symmetry.
0x10
And it appears to be mostly intact from how I remembered it a year or so ago.
Steve Peters
The formatting seems a bit off ( =head2 as opposed to == ... == ). Is
this easier to fix progromatically, or should I be editing as I read?
--WikiGnome
Ian Langworth wrote:
On Jan 26, 2005, at 3:48p, [EMAIL PROTECTED] wrote:
My main gripe is that the infrastructure for it is less OO friendly. The
example with the HTML output was awesome..until i looked at how it
was
done. The inability to get a data structure back for the test results
is v
On Tue, 22 Feb 2005 11:37:21 -0800, "Larry Wall" <[EMAIL PROTECTED]> said:
> or our great-grandchildren
> will curse our lack of foresight.
>
> Larry
It won't matter then anyway...Perl 25 code will come straight from our
brainwaves:
_
__...---'-`---...__
_===
On 2005-02-22 at 14:26:04, Juerd wrote:
>I think \777 should be chr(777). As should \0d777, should you want to
>document that it's really not octal. (Important mostly the first year
>after the first release.)
I don't think you can assume it'll only be confusing for a year. For
one thi
Chromatic wrote:
1) an optional description of a test, which occurs after the test number
but precedes an optional '#' character and anything following until the
newline character, having no effect on parsing
Summary?
That's what the one line short description in Bugzilla is called.
--Peter
On Tue, Feb 22, 2005 at 02:47:53PM -0500, Mark J. Reed wrote:
: Incidentally, will \o, \x, and the hypothetical \d still work without
: curlies for a certain number of digits but require curlies for larger
: numbers? I'd rather see consistency there.
Well, we switched to square brackets for those
On 2005-02-22 at 15:47:08, Larry Wall wrote:
>Maybe \x is short for \0x and that also gives us \0o, \0d and \0b,
>plus any other radix we come up with, assuming we decide it isn't
>overly ambiguous with bare \0.
Works for me. So when you really do want a \0 in the middle of a string
f
This patch adds a test to t/06sub.t to check that a closure returned by
a subroutine can find the variable that it is closed on.
But in writing this test I found that "if (die 'foo') { }" doesn't die, so a
test for that has been added to t/base/if.t.
And finally "my $foo; eval '$foo = die "bool"'
Peter Kay wrote:
The formatting seems a bit off ( =head2 as opposed to == ... == ). Is
this easier to fix progromatically, or should I be editing as I read?
Too late, I changed it!
--Peter
Aldo Calpini wrote:
Damian Conway wrote:
>@s = 'item' _ [EMAIL PROTECTED];
That's:
@s = 'item »_« @x;
(just checking that my unerstanding is correct, don't want to be
nitpicking :-)
assuming that you meant to prepend the string "item" to each element of
@x, isn't that:
@s = 'i
Rod Adams wrote:
This is my major point of the post. In my opinion, your example of:
# Print a list of substrings...
my $substring = substr("junctions", any(1..3), any(3..6));
say $substring.values();
Is a perfect example of a place where saying:
# Print a list of substrings...
my @s
Hello all & Autrijus,
I managed to get some time today to hack out some tests for PUGS. The
attached file contains a number of test for 'for'.
I based these test on what I read in the Exegesis 4
(http://www.perl.com/lpt/a/2002/04/01/exegesis4.html) about how 'for'
should work. A number of the t
> "DC" == Damian Conway <[EMAIL PROTECTED]> writes:
DC> my %seen is shape(IO) of Bool; # %seen maps IO objects to boolean
values
DC> while get_next_input_stream() -> $in {
DC> next if %seen{$in};
DC> $text ~= slurp $in;
DC> %seen{$in} = 1;
DC
Perl 6 Summary for 2005-02-08 through 2005-02-22
All~
Welcome to yet another fortnight summary. Lately p6l has been out
stripping p6i in volume. While this used to be the norm, lately it has
become a rare occurrence. Strange... Anyway, this summary would be
brought to you buy c
On Tue, Feb 22, 2005 at 12:50:01PM -0500, Peter Kay wrote:
> >And it appears to be mostly intact from how I remembered it a year or so
> >ago.
> >
> >Steve Peters
>
> The formatting seems a bit off ( =head2 as opposed to == ... == ). Is
> this easier to fix progromatically, or should I be editi
On Tue, Feb 22, 2005 at 03:40:55PM -0500, Peter Kay wrote:
> Chromatic wrote:
> >1) an optional description of a test, which occurs after the test number
> >but precedes an optional '#' character and anything following until the
> >newline character, having no effect on parsing
>
> Summary?
Summa
After some distractions I got back to this today.
After doing the merge and resolving all the conflicts (of which there really
weren't that many), I get it to build, and then get a:
0x0002c3b0 in string_index (interpreter=0xd001a0, s=0x3002fd8, idx=0) at
src/string.c:747
747 return (INTVA
in src/library.c (main branch), I find:
const char*
Parrot_get_runtime_prefix(Interp *interpreter, STRING **prefix_str)
{
static STRING *s;
static int init_done;
static const char *prefix;
int free_env;
char *env;
if (!*runtime_prefix)
return NULL;
if (!init_done) {
Attached is a patch for t/op/not.t. This is a nearly direct port of the
t/op/not.t in bleadperl. Missing though is a comparison against a
boolianized undef, which I don't know if it exists in Perl 6 or not.
Enjoy!
Steve Peters
[EMAIL PROTECTED]
--- /dev/null 2005-02-19 03:47:20.626125536 -0
A recent bug that showed up in Perl 5 caused a few people to wonder what
the purpose of C. It worked up to Perl 5.6 and returned the same
value as C. Starting with 5.6, it just core dumped. This has been
fixed it in the current bleadperl to go back to its original functionality of
behaving li
On Tue, Feb 22, 2005 at 10:21:00PM -0600, Steve Peters wrote:
: A recent bug that showed up in Perl 5 caused a few people to wonder what
: the purpose of C. It worked up to Perl 5.6 and returned the same
: value as C. Starting with 5.6, it just core dumped. This has been
: fixed it in the cur
YAPC::NA 2005 (Yet Another Perl Conference, North America) has just
released its call-for-papers; potential and aspiring speakers can
submit a presentation proposal via:
http://yapc.org/America/cfp-2005.shtml
The dates of the conference are Monday - Wednesday 27-29 June 2005.
Damian Conway wrote:
Rod Adams wrote:
This is my major point of the post. In my opinion, your example of:
# Print a list of substrings...
my $substring = substr("junctions", any(1..3), any(3..6));
say $substring.values();
Is a perfect example of a place where saying:
# Print a list of s
Michele Dondi wrote:
> OTOH all these discussions seem to imply that there is some demand (by
> me, for one!) for a "set-like" builtin data-type as well as for the
> already existing hashes and junctions and of course for
> interoperability between any two of them, e.g. in terms of automatic
> c
Hello all,
I have attached a patch for t/op/join.t, it adds 2 failing (TODO) tests
and 3 passing tests (for a total of 6). It attempts to cover all of the
basic variants of using join().
Let me know if there is any issues.
Thanks,
- Stevan
t_op_join.patch
Description: Binary data
Hello,
Another new test. This one just tests that basic anon subs and blocks
work correctly. Nothing all that special really, just 3 simple tests.
Again, if there are any issues, let me know.
Thanks,
- Stevan
anon_block.t
Description: Binary data
56 matches
Mail list logo
