ions and printing them without gist. Sorry!
--
Met vriendelijke groet, // Kind regards, // Korajn salutojn,
Juerd Waalboer
TNX
ions and printing them without gist. Sorry!
--
Met vriendelijke groet, // Kind regards, // Korajn salutojn,
Juerd Waalboer
TNX
32 $uint32 = 0x; $uint32++; is($uint32, 0, d 32);
my uint64 $uint64 = 0x; $uint64++; is($uint64, 0, d 64);
}
--
Met vriendelijke groet, // Kind regards, // Korajn salutojn,
Juerd Waalboer
TNX
nd regards, // Korajn salutojn,
Juerd Waalboer
TNX
Korajn salutojn,
Juerd Waalboer: Perl hacker <[EMAIL PROTECTED]> <http://juerd.nl/sig>
Convolution: ICT solutions and consultancy <[EMAIL PROTECTED]>
My suggestion:
consequential blocks
--
Met vriendelijke groet, Kind regards, Korajn salutojn,
Juerd Waalboer: Perl hacker <[EMAIL PROTECTED]> <http://juerd.nl/sig>
Convolution: ICT solutions and consultancy <[EMAIL PROTECTED]>
Brandon S. Allbery KF8NH skribis 2008-04-10 19:41 (-0400):
> On the other hand, that may be the answer right there: "when-blocks".
No, this is a when block:
when /foo/ { ... }
:)
--
Met vriendelijke groet, Kind regards, Korajn salutojn,
Juerd Waalboer: Perl hacker <
ly.
Good point. My Dutch-biased self doesn't have that wisdom :)
--
Met vriendelijke groet, Kind regards, Korajn salutojn,
Juerd Waalboer: Perl hacker <[EMAIL PROTECTED]> <http://juerd.nl/sig>
Convolution: ICT solutions and consultancy <[EMAIL PROTECTED]>
Larry Wall skribis 2008-02-21 11:15 (-0800):
> On Thu, Feb 21, 2008 at 01:29:05PM +0100, Juerd Waalboer wrote:
> : Then backtracking would happen, or more likely: Perl 6 would die. If
> : this community cannot come up with a virtual machine that can handle
> : Perl 6, then many peop
coming from?
It shows progress, and several well known, trusted and skilled hackers
work on it.
--
Met vriendelijke groet, Kind regards, Korajn salutojn,
Juerd Waalboer: Perl hacker <[EMAIL PROTECTED]> <http://juerd.nl/sig>
Convolution: ICT solutions and consultancy <[EMAIL PROTECTED]>
delijke groet, Kind regards, Korajn salutojn,
Juerd Waalboer: Perl hacker <[EMAIL PROTECTED]> <http://juerd.nl/sig>
Convolution: ICT solutions and consultancy <[EMAIL PROTECTED]>
antics, but do give Bufs support for
transparent en-/decoding, and perhaps even unicode semantics.
--
Met vriendelijke groet, Kind regards, Korajn salutojn,
Juerd Waalboer: Perl hacker <[EMAIL PROTECTED]> <http://juerd.nl/sig>
Convolution: ICT solutions and consultancy <[EMAIL PROTECTED]>
orajn salutojn,
Juerd Waalboer: Perl hacker <[EMAIL PROTECTED]> <http://juerd.nl/sig>
Convolution: ICT solutions and consultancy <[EMAIL PROTECTED]>
to for modules:
Modules can keep .pm, and the interpreter can tell whether it's Perl 5
or Perl 6, because Perl 6 modules have different keywords.
Personally I'm hoping for some extra abstraction in module filenames, to
allow UTF-8 module names with ASCII filenames.
--
Met vriendelijke
(sounds paradoxal), I
can create a separate virtual machine for that.
--
Met vriendelijke groet, Kind regards, Korajn salutojn,
Juerd Waalboer: Perl hacker <[EMAIL PROTECTED]> <http://juerd.nl/sig>
Convolution: ICT solutions and consultancy <[EMAIL PROTECTED]>
sing the code. Unpaid non-opensource code usually stays at ""...
My excuse is growing up with BASIC.
--
Met vriendelijke groet, Kind regards, Korajn salutojn,
Juerd Waalboer: Perl hacker <[EMAIL PROTECTED]> <http://juerd.nl/sig>
Convolution: ICT solutions and consultancy <[EMAIL PROTECTED]>
cumfix:<" "> := "e:.assuming(:!c);
Hm, would the following work?
given "e:.assuming(:!c) -> &circumfix:<" "> {
...
}
--
Met vriendelijke groet, Kind regards, Korajn salutojn,
Juerd Waalboer: Perl hacker <[EMAIL PROTECT
review current standards for method
> declaration; last I'd checked, the invocant did not need to be
> explicitly named.
It does if you want to access it by a name other than a lone sigil.
--
Met vriendelijke groet, Kind regards, Korajn salutojn,
Juerd Waalboer: Perl hacker <[EMAI
XML type would only serve to antiquate Perl 6 long before
> it's time (!), and is therefore a ... nonstarter.
Amen.
--
Met vriendelijke groet, Kind regards, Korajn salutojn,
Juerd Waalboer: Perl hacker <[EMAIL PROTECTED]> <http://juerd.nl/sig>
Convolution: ICT solutions and consultancy <[EMAIL PROTECTED]>
s it useful at all?
Absolutely!
> * Is it possible to implement it satisfactory without building a p6
> compiler?
Yes. Just match individual literal symbols. Someone looking for * should
encounter all uses of *, including ** and **{}.
> * Do you have a good idea for a project name?
l way.)
And this ambiguity is, IMO, more than enough reason to disallow this. As
for the end weight problem, try formatting the thing in three lines like
I do. That quickly makes it readable again:
system $?OS eq any
?? 'cls'
!! 'clear';
This puts "system
d this by default, because it would make it
easier for vendors to choose to use Perl in their base system. It would
also make Perl a more attractive choice for embedded systems.
--
korajn salutojn,
juerd waalboer: perl hacker <[EMAIL PROTECTED]> <http://juerd.nl/sig>
convolution:
standards
(Web, POD, ...), this is our one chance to get it right, for the next
two decades.
This said, I don't think Web should be core. It should be the *first*
web toolkit for Perl 6, though.
--
korajn salutojn,
juerd waalboer: perl hacker <[EMAIL PROTECTED]> <http
e gained by pre-empting this and picking
> something initially.
I disagree very strongly.
--
korajn salutojn,
juerd waalboer: perl hacker <[EMAIL PROTECTED]> <http://juerd.nl/sig>
convolution: ict solutions and consultancy <[EMAIL PROTECTED]>
o ever have consistent, semantic, structured OO
documentation throughout CPAN (and numerous in house projects), we must
start with Perl itself, and there isn't the option of having this tool
be third party.
--
korajn salutojn,
juerd waalboer: perl hacker <[EMAIL PROTECTED]> <http://ju
ld
still generate it from something else. A few macros could help ignore
the inline documentation.
--
korajn salutojn,
juerd waalboer: perl hacker <[EMAIL PROTECTED]> <http://juerd.nl/sig>
convolution: ict solutions and consultancy <[EMAIL PROTECTED]>
Zev Benjamin skribis 2007-06-11 0:57 (-0400):
> ?? and !! could always return some kind of result object that boolizes
> to true or false.
Can we *please* keep simple things simple?
--
korajn salutojn,
juerd waalboer: perl hacker <[EMAIL PROTECTED]> <http://juerd.nl/sig
.html
I couldn't find how to loop over multidimensionally shaped arrays; maybe
you can and maybe someone can show an example.
...Are you sure you were asking about Perl 6?
--
korajn salutojn,
juerd waalboer: perl hacker <[EMAIL PROTECTED]> <http://juerd.nl/sig>
convoluti
Dictionaries are usually alphabetically ordered. Hashes are not.
--
korajn salutojn,
juerd waalboer: perl hacker <[EMAIL PROTECTED]> <http://juerd.nl/sig>
convolution: ict solutions and consultancy <[EMAIL PROTECTED]>
his does not work with pugs, so I don't know if I am wrong, or
pugs is wrong.
--
korajn salutojn,
juerd waalboer: perl hacker <[EMAIL PROTECTED]> <http://juerd.nl/sig>
convolution: ict solutions and consultancy <[EMAIL PROTECTED]>
Thomas Wittek skribis 2007-05-15 1:52 (+0200):
> Would it be a good idea to call methods on objects, that never thought
> of this methods?
Absolutely! Roles can be used for that too.
--
korajn salutojn,
juerd waalboer: perl hacker <[EMAIL PROTECTED]> <http://juerd.nl/sig
k
a language needs a good balance between symbols and letters comma and
for a programming language comma I think alternating between the two is
close to a perfect balance comma whereas in human languages once, every
$few (words) is.probably; "period"
--
korajn salutojn,
juerd waalboer: perl
list context:
my @quux = (@foo, @bar); # These arrays "foo" and "bar" flatten
my @quux = ($foo, $bar); # These arrays "foo" and "bar" do not
That's a subtle yet very useful distinction.
But this is "just" very handy, not important.
--
ng style. And since my
preferred style is different, I'm glad you're not designing Perl 6.
--
korajn salutojn,
juerd waalboer: perl hacker <[EMAIL PROTECTED]> <http://juerd.nl/sig>
convolution: ict solutions and consultancy <[EMAIL PROTECTED]>
se if we had line \
continuation characters in here, it would suddenly look a lot \
different. Did you, while reading this, pause, just before "different"?
--
korajn salutojn,
juerd waalboer: perl hacker <[EMAIL PROTECTED]> <http://juerd.nl/sig>
convolution: ict solutions and consultancy <[EMAIL PROTECTED]>
put" be?
The Perl Way:
%count $input (or %count input) looks wrong, error caught even before
compile time, programmer time and energy conserved.
| And how on earth would you write "object.foo()", where foo is a variable
| holding a reference to a method, not the name of the method, if you had
| no sigils?
The Perl Way:
$object.foo() calls the method called "foo".
$object.$foo() calls the method that is in the variable $foo.
--
korajn salutojn,
juerd waalboer: perl hacker <[EMAIL PROTECTED]> <http://juerd.nl/sig>
convolution: ict solutions and consultancy <[EMAIL PROTECTED]>
h: Perl is very hard to read for someone who
doesn't know Perl well enough. But that's practically true for almost
language, be it Python or Japanese.
--
korajn salutojn,
juerd waalboer: perl hacker <[EMAIL PROTECTED]> <http://juerd.nl/sig>
convolution: ict solutions and consultancy <[EMAIL PROTECTED]>
Darren Duncan skribis 2007-04-14 23:37 (-0700):
> Presumably Juerd will get back to these when he has the tuits, but
> meanwhile you could try improving what he started.
Indeed.
Please read these two posts to this list:
http://groups.google.nl/group/perl.perl6.users/browse_thread/
f needs a boolean output
template, but it would be nice if it were configurable.
--
korajn salutojn,
juerd waalboer: perl hacker <[EMAIL PROTECTED]> <http://juerd.nl/sig>
convolution: ict solutions and consultancy <[EMAIL PROTECTED]>
[EMAIL PROTECTED] skribis 2007-03-28 13:17 (-0700):
> +block) early using the C verb. More precidely, it leaves the
precisely?
--
korajn salutojn,
juerd waalboer: perl hacker <[EMAIL PROTECTED]> <http://juerd.nl/sig>
convolution: ict solutions and consultancy <[EMA
Juerd Waalboer skribis 2007-03-09 21:27 (+0100):
> Just a short note: please, if this is implemented, make sure that either
> Perl 6 conforms to Perl 5 behaviour, or the other way around.
Wanted to CC this list, but by accident replaced the To instead. Now
CC'ing p5p.
--
kora
Just a short note: please, if this is implemented, make sure that either
Perl 6 conforms to Perl 5 behaviour, or the other way around.
--
korajn salutojn,
juerd waalboer: perl hacker <[EMAIL PROTECTED]> <http://juerd.nl/sig>
convolution: ict solutions and consult
ojn,
juerd waalboer: perl hacker <[EMAIL PROTECTED]> <http://juerd.nl/sig>
convolution: ict solutions and consultancy <[EMAIL PROTECTED]>
Ik vertrouw stemcomputers niet.
Zie <http://www.wijvertrouwenstemcomputersniet.nl/>.
Thomas Wittek skribis 2007-03-03 23:17 (+0100):
> Larry Wall:
> > : if ($item = 'foobar') {
> == of course ;)
Or how about eq? :)
--
korajn salutojn,
juerd waalboer: perl hacker <[EMAIL PROTECTED]> <http://juerd.nl/sig>
convolution: ict solutions
and a great idea.
I love it!
--
korajn salutojn,
juerd waalboer: perl hacker <[EMAIL PROTECTED]> <http://juerd.nl/sig>
convolution: ict solutions and consultancy <[EMAIL PROTECTED]>
Ik vertrouw stemcomputers niet.
Zie <http://www.wijvertrouwenstemcomputersniet.nl/>.
Yuval Kogman skribis 2006-11-22 16:01 (+0200):
> my $x ::= 3;
> sub foo { say ++$x };
Why would you be allowed to ++ this $x? It's bound to an rvalue!
--
korajn salutojn,
juerd waalboer: perl hacker <[EMAIL PROTECTED]> <http://juerd.n
ve in different places, so you can just use a
normal postfix operator:
sub postfix: ($lhs) {
$CALLER::_ = $lhs;
}
42?;
say($_); # prints 42!
# This code is not futuristic. It already works with Pugs.
But you wanted a statement thingy. That would require that you modif
ion matches
Can't this be generalized somehow? Return an lvalue proxy, like substr
does, and make thunking the default for certain LHS types.
I don't like special syntax that looks like normal syntax.
--
korajn salutojn,
juerd waalboer: perl hacker <[EMAIL PROTECTED]> <htt
TF-8 string.
I propose that using :bytes on a text string throws an exception.
--
korajn salutojn,
juerd waalboer: perl hacker <[EMAIL PROTECTED]> <http://juerd.nl/sig>
convolution: ict solutions and consultancy <[EMAIL PROTECTED]>
Ik vertr
quot;bar baz", # And
quux => "xyzzy",# comments
blah => "42#15",# go
red => "#FF0000", # here
);
but with much less punctuation and finger strain.
--
korajn salutojn,
juerd waalboer: perl hacker <[EMAIL PROTECTED
# 43, 16
[ 42, 15 ] »+ 1 # 2
[ 42, 15 ] »»+ 1 # [ 43, 16 ]
The ASCII variant is a bit big, but that's okay huffmanwise, IMO.
Recursion can be a pretty big operation anyway. Being explicit about
that is good.
--
korajn salutojn,
juerd waalboer: perl hacker <[EMAIL PROTECTED]&
all
bracketing delimiters the same there. Partly for future-proofness,
partly for least surprise.
--
korajn salutojn,
juerd waalboer: perl hacker <[EMAIL PROTECTED]> <http://juerd.nl/sig>
convolution: ict solutions and consultancy <[EMAIL PROTECTED]>
tatement modifier to a do block is
>specifically disallowed
Oh. For some reason, I thought this exception was for loops only.
--
korajn salutojn,
juerd waalboer: perl hacker <[EMAIL PROTECTED]> <http://juerd.nl/sig>
convolution: ict solutions and consultancy <[EMAIL PROTECTED]>
for that! :)
say 1 if 1 and 1 and 1;
Oh, and 1 is always true. So you could just write:
say 1;
Which seems like a great improvement.
It may be more useful to discuss this issue using less contrived
examples. :)
--
korajn salutojn,
juerd waalboer: perl hacker <[EMAIL PROT
opriate.
I think you meant either:
my @add = $string xx $repeat;
or:
my $add = $string x $repeat;
Or perhaps:
my $add = [ $string xx $repeat ];
# This is what your current code does, but I think it's best if Perl
# enforced that you be explicit about the [].
--
korajn sa
ail now, for you to form an opinion.
--
korajn salutojn,
juerd waalboer: perl hacker <[EMAIL PROTECTED]> <http://juerd.nl/sig>
convolution: ict solutions and consultancy <[EMAIL PROTECTED]>
uld work for that. Why you'd want one beats me.
Generated code. It's nice that Perl usually isn't picky about such
things, because it saves you a lot of special cases when you're
generating code.
--
korajn salutojn,
juerd waalboer: perl hacker <[EMAIL PROTECTED]&
MAIL PROTECTED]), then
> what do we call what
> the \ is doing there, now that references are supposed to be a
> behind-the-scenes automagical thing?
They're captures.
I personally wouldn't mind unary $, to supplement unary @ and %.
--
korajn salutojn,
juerd waalboer:
Some pseudo-code for illustration. Maybe we should put this on version
control or wiki, and collectively hack on it. If we can agree on any
certain route.
If anyone wants to go ahead and implement things, don't wait for me
please. I unfortunately do not have the tuits to do this in full. I
don't e
space, and making it use information from the
Web object (which mostly delegates to its .request and .response),
doesn't have to mean it can't be used stand-alone.
--
korajn salutojn,
juerd waalboer: perl hacker <[EMAIL PROTECTED]> <http://juerd.nl/sig>
convolution: ict solutions and consultancy <[EMAIL PROTECTED]>
6, not Pugs specifically. It's known that
Pugs doesn't implement all of Perl 6 perfectly yet, and Perl 5
compatibility is one of the many things that needs improvement. Give it
some time, and don't draw conclusions already.
--
korajn salutojn,
juerd waalboer: perl hacker &l
the syntax for an empty slice then?
--
korajn salutojn,
juerd waalboer: perl hacker <[EMAIL PROTECTED]> <http://juerd.nl/sig>
convolution: ict solutions and consultancy <[EMAIL PROTECTED]>
ld fashioned :)
A style guide is very hard to write. It indeed boils down to fluency.
--
korajn salutojn,
juerd waalboer: perl hacker <[EMAIL PROTECTED]> <http://juerd.nl/sig>
convolution: ict solutions and consultancy <[EMAIL PROTECTED]>
A. Pagaltzis skribis 2006-09-20 22:39 (+0200):
> * Juerd <[EMAIL PROTECTED]> [2006-09-20 22:25]:
> > I think it's time we moved away from the param method, and
> > started using a hash.
> I don???t know about that. The `param` method has the nice property
> that it
ing
a hash. In fact, two hashes, get and post.
use Web <$web>;
$web.get;
$web.post;
$web; # shorthand form for $web.post // $web.get
--
korajn salutojn,
juerd waalboer: perl hacker <[EMAIL PROTECTED]> <http://juerd.nl/sig>
convolution: ict solutions and consultancy <[EMAIL PROTECTED]>
mode is perl5:CGI, that loads the old Perl 5 CGI.pm.
There's little need for us to port bad things to Perl 6. Peoplo who
really want or need to use them can, and we should concentrate on
creating something that's GOOD for new code. This said, I do think it'd
be wise to document chang
uing about
> namespace usage here :))
Yes. I'm talking about a web development toolkit, that does at least
what CGI.pm did, and not about CGI as a namespace, because I think
that's an incredibly bad thing anyway.
--
korajn salutojn,
juerd waalboer: perl hacker <[EMAIL PROTECTED]> <http://juerd.nl/sig>
convolution: ict solutions and consultancy <[EMAIL PROTECTED]>
than that, it should be very lightweight and easy to
> use.
I agree that things should be lightweight and easy to use. But in Perl
6, that doesn't mean that you should avoid nicely structured OO.
--
korajn salutojn,
juerd waalboer: perl hacker <[EMAIL PROTECTED]> <http://juerd.nl/sig>
convolution: ict solutions and consultancy <[EMAIL PROTECTED]>
uce some real
convenience instead.)
--
korajn salutojn,
juerd waalboer: perl hacker <[EMAIL PROTECTED]> <http://juerd.nl/sig>
convolution: ict solutions and consultancy <[EMAIL PROTECTED]>
the items
> that fail the test, while 'reject' would filter out the ones that pass
> it.
There's a neat trick for this: .grep:{ not ... }
HTH :)
--
korajn salutojn,
juerd waalboer: perl hacker <[EMAIL PROTECTED]> <http://juerd.nl/sig>
convolution: ict solutions and consultancy <[EMAIL PROTECTED]>
t make sense to have a single .pm that does all this. There's
absolutely no need for having all these different tasks in one module.
There's not even any benefit. You can just as well use a couple of
nicely named, grouped, and reasonably standalone roles or classes, and
then a single module to
Richard Hainsworth skribis 2006-09-18 17:18 (+0400):
> However, I am using pugs from the debian package and not directly from
> the repository. So perhaps, the problem is I am not using the latest
> version of pugs.
That version is rather old in our universe :)
--
korajn salutojn,
lt, in a general purpose
web development library.
--
korajn salutojn,
juerd waalboer: perl hacker <[EMAIL PROTECTED]> <http://juerd.nl/sig>
convolution: ict solutions and consultancy <[EMAIL PROTECTED]>
Thaw.pm?
Interpolate the arrays:
while ("@numbers" ne "@{[ sort @numbers ]}") { ... }
--
korajn salutojn,
juerd waalboer: perl hacker <[EMAIL PROTECTED]> <http://juerd.nl/sig>
convolution: ict solutions and consultancy <[EMAIL PROTECTED]>
Amir E. Aharoni skribis 2006-09-17 17:22 (+0300):
> 17/09/06, Juerd <[EMAIL PROTECTED]> skribis:
> > This is a very strict language, though, as it is based on XML.
> > A document is either valid and unambiguous, or completely invalid.
> Just like any programming language s
in one place and then used by
every part of the toolkit. At the same time, these things should be
overridable at any point. That can be done by temp'ing an attribute, for
example.
Next time I will write something about implementation. This will partly
be from the perspective of implementation
still takes up to a minute for rakudo.org pages to
load on my home machine.
--
korajn salutojn,
juerd waalboer: perl hacker <[EMAIL PROTECTED]> <http://juerd.nl/sig>
convolution: ict solutions and consultancy <[EMAIL PROTECTED]>
Mark Stosberg skribis 2006-09-16 22:04 (-0500):
> As far as I'm aware, no work on CGI::Session for Perl 6 has started yet.
I'm happy about that, because this module must not have "CGI" in its
name.
--
korajn salutojn,
juerd waalboer: perl hacker <[EMAIL PROTECT
o been seen now well
> calls to Perl 5 modules can work for the general case.
Please note that eventually, perl5:CGI is supposed to work as expected.
--
korajn salutojn,
juerd waalboer: perl hacker <[EMAIL PROTECTED]> <http://juerd.nl/sig>
convolution: ict solutions and consultancy <[EMAIL PROTECTED]>
that nobody can actually recall, and based
precisely 88.445% on the writer's own experience.
--
korajn salutojn,
juerd waalboer: perl hacker <[EMAIL PROTECTED]> <http://juerd.nl/sig>
convolution: ict solutions and consultancy <[EMAIL PROTECTED]>
et=iso-8859-1';
# implies: $response1.encoding = 'iso-8859-1;
$response2.type = 'application/xml';
$response2.encoding = 'UTF-8';
my $response3 = Web::Response.new :type('text/html;
charset=iso-8859-1');
my $response4 = Web::Response.new :type,
:encoding;
--
korajn salutojn,
juerd waalboer: perl hacker <[EMAIL PROTECTED]> <http://juerd.nl/sig>
convolution: ict solutions and consultancy <[EMAIL PROTECTED]>
#x27;t fix the shorthand syntax for testing -e on $_ at all,
because .'-e' is no better than -e($_). Well, okay, 1 character, but it
costs a lot of grokability.
--
korajn salutojn,
juerd waalboer: perl hacker <[EMAIL PROTECTED]> <http://juerd.nl/sig>
convolution: ict solutions and consultancy <[EMAIL PROTECTED]>
Juerd skribis 2006-09-15 23:26 (+0200):
> Randal L. Schwartz skribis 2006-09-15 9:15 (-0700):
> > The thing that CGI.pm does is put in one place everything you need for a
> > simple web form. And there's an amazing number of applications for
> > this... putting
the .* variants, not to mention generating method
> names by interpolation without needing a temp variable.)
First impressions:
Ugly, hard to type, not a solution for -e, weird syntax.
--
korajn salutojn,
juerd waalboer: perl hacker <[EMAIL PROTECTED]> <http://juerd.
out the simplicity of CGI.pm's basic task handling: parsing
> the incoming parameters (including file upload), and generating sticky forms
> and other common HTML elements.
Don't thow out the simplicity, but do severely re-model things!
--
korajn salutojn,
juerd waalboer: perl hacker
t 9th about the -X filetest
> operators between at least audreyt, Juerd, myself and markstos. The
> problem with these operators was that they conflicted in some cases with
> the parsing of unary -, such as:
> foo(-?? * 2 * $r);
> or just:
> sub x($n) { $n*2 }
Aankhen skribis 2006-09-14 17:00 (-0700):
> There were a few discussions with Juerd and others in #perl6 about
> CGI.pm in Perl 6...
I've been following the discussion with great interest, and will
summarize my thoughts here soon.
--
korajn salutojn,
juerd waalboer: perl hack
then.
Just ignoring the declaration is bad, just like implicit declaration. If
we do this, we get only typo checking, and none of the other nice
protection that lexical declaration gives us.
--
korajn salutojn,
juerd waalboer: perl hacker <[EMAIL PROTECTED]> <http://juerd.nl/sig&g
presses...
"And since it's something used a lot in expressions, you wouldn't use
the parenless form of the method call much."
Juerd
--
http://convolution.nl/maak_juerd_blij.html
http://convolution.nl/make_juerd_happy.html
http://convolution.nl/gajigu_juerd_n.html
ject, so you'd need a different explanation...
> I do not think that C should mutate its LHS, regardless what its RHS
> is.
Agreed, and that's why "$foo but s///" would be a reasonable replacement
for what's currently still "$foo.subst(//, '')".
ecause we have stuff like
:2nd and :3th. And if we're parsing anyway, you might as well pass in a
string. Indeed, :g would only be syntactic sugar.
Juerd
--
http://convolution.nl/maak_juerd_blij.html
http://convolution.nl/make_juerd_happy.html
http://convolution.nl/gajigu_juerd_n.html
think that's a pretty intuitive
> way of handling the problem.
It is indeed a modifier on the *match*, or the *substitution*. Just not
on the *regex*. What you pass to a .subst method is a regex, not a
match. The difference is that matches and substitutions are actions,
while a
/ postfix op mainly stems from this argument, but
I really also believe that ~~ and s/// is a farfetched combination. Perl
5's =~ was a binding operator, and s/// fit right in. But Perl 6's ~~ is
a matching operator, and in my opinion should remain pure, and so: not
mutate.
I'm even a bit in
f called "s") is good huffman
coding. My expectation is that copying substitution will be used much -
perhaps even more than mutating substitution!
$foo.subst(/foo/, "bar")
$foo.s(/foo/, "bar")
$foo.s/foo/bar/
Hm. I don't know how "but"
can easily replicate.
I personally still prefer $foo.s/// and $foo.=s///, because I don't
think substitution belongs in a smart match op.
Juerd
--
http://convolution.nl/maak_juerd_blij.html
http://convolution.nl/make_juerd_happy.html
http://convolution.nl/gajigu_juerd_n.html
Damian Conway skribis 2006-08-31 9:08 (+1000):
> return want.rw ?? $lvalue
> :: want.count == 2 ?? (7,11)
> :: want.item ?? 42
> :: want.list ?? 1..10
> ::die "Bad context;
s:g/::/!!/ #
must say I'm a bit surprised that you hadn't heard of feather before.
Apparently I should try even harder to get the word out.
Juerd
--
http://convolution.nl/maak_juerd_blij.html
http://convolution.nl/make_juerd_happy.html
http://convolution.nl/gajigu_juerd_n.html
a factor 260) and you don't need to sacrifice surfing
speed for it.
Also, feather has RAID 1 for its harddisks, and daily backups to another
host.
Juerd
--
http://convolution.nl/maak_juerd_blij.html
http://convolution.nl/make_juerd_happy.html
http://convolution.nl/gajigu_juerd_n.html
ather is in.
Juerd
--
http://convolution.nl/maak_juerd_blij.html
http://convolution.nl/make_juerd_happy.html
http://convolution.nl/gajigu_juerd_n.html
| | | Class
> B |
> |
> --|
> |Class C |
> ----
I'm curious what this was supposed to look like. :)
Juerd
--
http://convolution.nl/maak_juerd_blij.html
http://convolution.nl/make_juerd_happy.html
http://convolution.nl/gajigu_juerd_n.html
1 - 100 of 764 matches
Mail list logo
