Jon Lang wrote:
smuj wrote:
I'd personally prefer it if Ranges just did lists, including when smart
matching, but had an interval method or such like for explicit matching
against the endpoints, e.g.
2.5 ~~ interval(1..5) # or
2.5 ~~ $myrange.interval
I don't like the Huffma
rval method or such like for explicit matching
against the endpoints, e.g.
2.5 ~~ interval(1..5) # or
2.5 ~~ $myrange.interval
I'm new in town though, so I'll happily admit that I don't know the full
implications of such a change. Having context-insensitive Ranges DWIM's
better to me, but DWIMery, like beauty, is clearly in the eye of the
beholder! :)
Cheers,
--
smuj
while.
Thank you O Great Decider!!
Cheers
--
smuj
Jon Lang wrote:
smuj wrote:
Jon Lang wrote:
Here's a radical notion: use something other than '#' to initiate an
inline comment.
[snippage]
Or maybe just don't allow "embedded" comments unless they are actually
"embedded", i.e. if a line starts wit
Jon Lang wrote:
smuj wrote:
smuj wrote:
Jon Lang wrote:
... the biggest potential stumbling block for this
would be the existence of a double-bracket that sees frequent use at
the start of a line. Query: does '<<' count as a double bracket, or
as a single bracket (since it
smuj wrote:
Jon Lang wrote:
On Mon, Aug 10, 2009 at 2:16 PM, Mark J. Reed wrote:
I still like the double-bracket idea. I don't much mind the extra
character; 5 characters total still beats the 7 of HTML/XML.
Agreed. As I said, the biggest potential stumbling block for this
would b
up.
[S02] {Note however that bare circumfix or postcircumfix <<...>> is not
a user-selected bracket, but the ASCII variant of the «...»
interpolating word list. Only # and the q-style quoters (including m, s,
tr, and rx) enable subsequent user-selected brackets.}
Cheers,
--
smuj
Patrick R. Michaud wrote:
On Mon, Aug 10, 2009 at 06:46:34PM +0100, smuj wrote:
Although I can see some minimal uses for embedded comments, I think in
general the cost/benefit ratio isn't enough to warrant their existence.
I could be wrong of course! :-) I'd like to know if anyon
s altogether
2) ## followed by _any_ opening bracket character is an embedded comment
It would be nice to hear p6l-ers' reactions on these two proposals. Be
warned, though -- this is a bit of a bikeshedding topic. :) Every one
and his dog is an expert on comment syntax.
I think that's something we can all agree on!! :-)
[0] http://use.perl.org/~masak/journal/39334
[1] http://use.perl.org/comments.pl?sid=43438&cid=69583
Cheers
--
smuj
ing if it's
> pure digits with optional '-' on the front would not be any more
> inefficient.
Do we still get to keep the current semantics if we specificially declare a
string? e.g.
my Str $x = "-100";
$x++;
say $x; # prints -101
my $y = "-100";
$y++;
say $y; # prints -99
Cheers,
smuj
--
smuj
([EMAIL PROTECTED])
On Thursday 24 April 2008 23:54, smuj wrote:
> There's plenty of other ways to confuse people too; try $x with "999" or
> "1.23e9" :-)
One can even confuse oneself! Forget the dot in "1.23e9" :-)
Cheers,
smuj
--
smuj
([EMAIL PROTECTED])
plenty of other ways to confuse people too; try $x with "999" or
"1.23e9" :-)
Cheers,
smuj
--
smuj
([EMAIL PROTECTED])
12 matches
Mail list logo
