ould have a s/z/s/ version, for
those who speak a z-impared dialect of English.)
-=- James Mastros
name than 'regex'.
[...]
> Maybe 'match' is a better keyword.
Can I suggest we keep match meaning thing you get when you run a thingy
against a string, and make "matcher" be the thingy that gets run?
100% agree with you, Allison; thanks for putting words to "doesn't feel
right".
-=- James Mastros
ements, but
it compares as a range. 1.1 should ~~ 1..2; pugs thinking that's false is a
bug, not a feature.
Of course, that doesn't mean implementing range in a subset of perl6 without
it isn't interesting, and possibly useful for bootstrapping.
-=- James Mastros
infix .new.
>
> (args)`Class;
The problem with it is that somehow we have to get 5`m / 30`s to work,
even though m is an operator, which AFAIK means it needs to be a macro,
or the moral equivalent (is parsed).
Also, having every unit be a like-named class would very muc
should be looking into how to make it a pragmata,
rather then pushing the idea on perl6-language. It shouldn't be too
hard -- a matter of using the equivalent of perl5's UNIVERSAL::AUTOLOAD,
and the OUTER:: scope.
-=- James Mastros,
theorbtwo
role into some
> class or other to determine the behavior if they care.
Why is this a role, rather then just implementing postcircumfix:«[
]»(Whatever $self: Int $index) ? (I'd hope the error message is a bit
more newbie-friendly, but that's the only special-casing I see it
needing...)
-=- James Mastros
don't like CGI.pm's HTML generation, for example
-- it makes you feel like you don't need to know HTML, when you do.)
-=- James Mastros
rom DEM to FRF,
you /must/ convert to EUR in the middle, or you will get the wrong
result. Of course, neither the DEM nor the FRF have existed in several
years, so it probably isn't that important...)
-=- James Mastros,
Who certainly looks forward to this.
hogonality strikes again.
...unless read returns a Str but source("foo").
-=- James Mastros
Luke Palmer wrote:
James Mastros writes:
Does this imply that it's now possible to type C, and
declare @foo? In the current perl, this doesn't work -- it's a syntax
error. It'd certainly make many constructs easier.
That looks weird to me. But as Rod points out, it can b
's a syntax
error. It'd certainly make many constructs easier.
-=- James Mastros
th literals. (The dot
there is optional.) (Until a little bit ago, that was $wheel.<>
or $wheel.«roll». (Note that I had to switch keyboard layouts again to
type that.))
-=- James Mastros
I'm sure they're there somewhere.)
-=- James Mastros
*I think I just broke two or three commandments.
ile trying, and apparently
failing, not to).
-=- James Mastros
"exotic" characters to the exotic behaviors,
and leave the angles with their customary uses.
...of which they have plenty already. Backtick has exactly one, and not
an often-used one at that... I'm fine with axing it. Of course, there
are a lot more people in the world then just me.
If you're a White Russian I suppose the yolk is on me.
In Russia, the yokes throw you!
-=- James Mastros,
theorbtwo
t least a description of their declarations).
-=- James Mastros,
theorbtwo
d seem, then, that the answer is "there's some property of
thingies that gives the name that error messages will use to refer to
them". (I want to thank the man who made "thingy" the proper technical
term, BTW.) So what's it called?
-=- James Mastros
Nicholas Clark wrote:
On Tue, Sep 07, 2004 at 06:07:24PM +0200, James Mastros wrote:
4. The single-file, platform dependent, machine language executable
(realexe).
Which parrot can already do. (Or at least could, but I don't think that
anyone's been checking on it recently)
Er, right --
minimal. The
others require standard-library support, but all the major bits are
things that should already be in the standard library (because a
front-end to C6PAN should come with, and that means extracting some sort
of .tar.gz files -- calling out to external utilities doesn't cut it t
normal quotes.
3) Some editors will give you one when you want the other.
- David ³wondering how likely curly-quotes are to come out right² Green
4) Many people think they're in Latin-1, but they aren't, they're only
in Microsoft's perversion of Latin-1.
-=- James Mastros
he difference between x and xx is sensical -- the
former repeats one thing, the later many... but what's the reasoning for
xxx, other then that it's like xx? How will users be able to remember
which is which?
-=- James Mastros,
theorbtwo
on't disturb useful things that you'd want in
double-quotes -- which includes patterns common in any natural language,
which includes even the literal versions of << / >> (which I can't type
easily at the moment).
-=- James Mastros
Austin Hastings wrote:
So, how wrong is this:
class VerticalYadda
{
extends Yadda;
multi method coerce:as($what) {
say "Coercing VerticalYadda to " ~ ($what as Str);
next METHOD;
}
}
sub *\U{VERTICAL ELLIPSIS}()
{
return new VerticalYadda;
}
=Austin
macro \
kup, that saves the expiry time,
and defining a second coercion from that to an IP address, that reruns
the lookup if the TTL has expired. The first coercion should take place
at compile time, the second not until runtime.
-=- James Mastros
e
mix of APL and PHP. At least we don't have a Unicode alias for say
(yet, why do I suspect we're about to get a unary » operator for it?
Perhaps I'm just pessimistic this morning.)
-=- James Mastros
Mark J. Reed wrote:
One obvious reason for reaching out to unicode characters is the
restricted number of non-alphanumeric characters in ASCII. But why do
infix operators have to be non-alphanumeric?
They don't - but they do have to "look like operators". Thanks to the
multiplication symbol, lowe
Karl Brodowsky wrote:
Mark J. Reed wrote:
The UTF-8 encoding is not so attractive in locales that make
heavy use of characters which require several bytes to encode therein, or
relatively little use of characters in the ASCII range;
utf-8 is fine for languages like German, Polish, Norwegian, Spanis
there's no way to tell if a future eval STRING
(or equiv) might be useful.)
-=- James Mastros
mod_perl get funded could give to the
first, and people who wanted to see Larry, you (Dan), Damian, and the
gang get funded (or, unfornatly, some subset thereof, depending on how
much money comes in) could give to the second... and everybody gets
their way.
-=- James Mastros
should be
unique across a process over all time.) If that'd require that an
object's ID be a combination of the header address and a generation
counter, that's OK. It means a serilization point in the allocator, but
I think we'd need one no matter what (Dan?).
-=- James Mastros
the option of
committing later. Sort of what a "try" block would like to be when
it grows up...
Or hypothetical variables in a non-regex context...
-=- James Mastros
s, unless someone can think of something useful
for it to mean.
It would, logicaly, mean that the class Module has a method "foo" if
true -- applying can on an object tells you if the class of that object
can do somthing, and Main is an object of class Module... right?
(%Main:: is a hash,
(This is a reply to a mail accidently sent to me personaly instead of
the list. Buddha, care to resend your other mail? I havn't quoted it
in total.)
On 12/12/2002 9:43 AM, Buddha Buck wrote:
James Mastros wrote:
Here's my basic defintion of ID: Two things should have the same
neccessarly have the
same reprensentation in PBC -- to whit, a constant float in different
compilation units will get different slots in the constant table, but
are really identical. The same is true of constant strings. (Constant
integers are inlined, and thus this doesn't apply t
esentation slides on this at
http://perl.plover.com/yak/memoize-quant/ -- "Quantitative Analysis of
Memoization".
-=- James Mastros
PS -- This is getting offtopic, even for p6l.
omthing_here($_);
die "Bye-bye universe!" if ($_=42);
}
Will never compute anything after the first 41 element in @foo occours.
(I'm assuming map, grep, and any other list-oriented function that can
get away with it will act lazily when given a lazy-list argument.)
-=- James Mastros
On 12/05/2002 12:18 PM, Michael Lazzaro wrote:
On Thursday, December 5, 2002, at 02:11 AM, James Mastros wrote:
On 12/04/2002 3:21 PM, Larry Wall wrote:
\x and \o are then just shortcuts.
Can we please also have \0 as a shortcut for \0x0?
\0 in addition to \x, meaning the same thing? I
ndows and several other OSes (I
think, I like to play with Unicode but have little actual use for it),
ALT-0nnn is spelt in decimal only. Decimal Unicode ordnals are
fundimently flawed (since blocks are always on nice even hex numbers,
but ugly decimal ones), but useful anyway).
-=- James Mastros
--
0101 \101 p5/C compatable Unintutive
0o101 \o101 ConsistentHard to read
0c101 \o101 keeps \c for Inconsistent
control-char
0c101 unsupported Consistentoctal string chars
unsupported
0t101 \t101 Consistentwhat's tab?
Or somthing else?
All choices are bad, which one is best?
-=- James Mastros
ly real benifit I see is typing ease, and -> isn't that
hard to type. That's what editor macros are for.
It's rather unfornate that we've run out of characters to use
for operators, but we've got to deal with it better then flipping
around operators willy-nilly.
-=- James Mastros
intended for, it seems like a very concise,
> expressive way to do multiple relationship tests without needing all those
> "&&"s and such.
Indeed. (Though, as defined above, this won't work on the string
operations, only the numerics.)
-=- James Mastros
it would be a plain hash, with funny-
character included in the key.
-=- James Mastros
sing
the comma operator. (Or did we get rid of the comma operator when
I wasn't paying attention?) If we do have @foo[(stuff)] make stuff
be in list context, then that'd be a special case (I think).
-=- James Mastros
ers) within one file, and having perl5 being another parser. Put them
together, and you get exactly this.
-=- James Mastros
).
That lets us keep for somthing iteratorish, which saves
special-caseing (I do occasionaly use a qw list with one element),
and lets us keep continuity.
Anyway, I'm fairly certian that I'll use iterators more then qw lists.
-=- James Mastros
ive), so I'd rather we stay with:
>$a = <$b>; # same as next $b or $b.next
> Hey, maybe we can convince Larry... ;-)
I'd tend to agree. Especialy that we don't need a qw() alternative.
However, I don't think Larry's in a convincable mood -- coughdotcough.
-=- James Mastros
and I think the use of := agrees with what is planned.
It also avoids the use of a verbose .next (and the dot, which I still don't
like ).
-=- James Mastros
9 !097!0!9080"; would
stop looking after it had found and returned 0!0 and 9, and never even
glance at the 98. Basicly, if you assign to a list of lvalues, @returnlist,
it
will stop looking after it has found scalar(@returnlist) matches or
end-of-input.
-=- James Mastros
If you want that, you could go with `, which could produce some
ambiguity, both with qx and with ', which looks very similar in many fonts.
BTW, I think that considering no-whitespace cases of indirect object is
quite silly -- does anybody acatualy use that?
This is the first I thought it wasn't a syntax error.
-=- James Mastros
ewhere on these threads: What does changing to "." from -> buy us?
I can see that "." is shorter to type then ->, but, say, \ would be just as
good. I can't really say changing because "." is more standard. It isn't
standard to C or perl5. It's possible to misparse "." as concat with "." as
a sepperator on version-strings, but that's more of a problem with using it
for method-call.
-=- James Mastros
you
really want to be able to read from a URL in one line, let yourself do
. But make opening a URL an explicit act.
> But I really mustn't spill too many half-digested beans here. :-)
If you have to, at least do it in the toilet.
> P.S. Larry's Second Law of Language Rede
't symlink
bunzip -> bunzip2 and bzip -> bzip2 and have it do the Right Thing. On the
gripping hand, when combined with other mesures, not so bad.
-=- James Mastros
--
The most beautiful thing we can experience is the mysterious. It is the
source of all true art and science. H
a better system, use
a site-policy file, or bite the bullet and change the #! lines.
-=- James Mastros
--
The most beautiful thing we can experience is the mysterious. It is the
source of all true art and science. He to whom this emotion is a stranger,
who can no longer pause to wond
arison for the same
> arguments.
Ahh, bingo. That's what a number of people (inculding me) are suggesting --
a :functional / :pure / :stateless / :somthingelseIdontrecall attribute
attachable to a sub.
-=- James Mastros
--
The most beautiful thing we can experience is the myster
o english as a command
form, telling the Cow to speak. (If you translate both -> and ' ' into a
comma.)
Anyway, I'm trying to argue lingustics in a perl ML, with zero training.
Is there a linguist in the house? (Hm, didn't Larry go to Japan to learn a
language with wierd
dvanced garbage collector, just like
> Scheme or Strongtalk compiler?
We want to make it as fast as reasonably possible. Writing a native
compiler might not be _reasonably_ possible. And an advanced GC will almost
certianly be part of perl6; they're orthogonal issues.
-=-
On Wed, Mar 28, 2001 at 05:57:30PM -0500, James Mastros wrote:
> [A bunch of stuff]
Oh, and I agree with sombody else on this thread that unless otherwise
stated, the sort should always assume statelessness (and thus the ability to
cache at will). If it's trivial to see that the sort
te such as
:simple or :stateless. So let it be spoken, so let it be done.
This isn't any more preverse then the "you can't assign to constants" rule.
-=- James Mastros
--
The most beautiful thing we can experience is the mysterious. It is the
source of all true art and
that increment a
counter every time they are accessed, for example.)
I think that the difference between 4&3 dosn't matter. We only have things
in 4 and not 3 that vary in abs(), but not sign.
We're left with 1&2, and for 1, the sort won't work anyway.
So long as we consid
>my_compare(b,c) < 0, then it should also be the case that
> >my_compare(a,c) < 0
I can't define it better then that. (Though there's more to it then that).
Note that only the sign of the answer is gaurnteed, so it doesn't even have
to be interna
")=123456
f(f("+123,456))=123456
The functon is not idempotent. Even if you checked f(x)==x (function is the
identity), an input of "123456" would work.
-=- James Mastros
--
The most beautiful thing we can experience is the mysterious. It is the
source of all true
On Mon, Mar 26, 2001 at 06:31:22PM -0500, Dan Sugalski wrote:
> At 04:04 PM 3/26/2001 -0500, James Mastros wrote:
> >The only way f(a) can not be stable and f(a) <=> f(b) can be is somthing of
> >a corner case. In fact, it's a lot of a corner case.
> You're ig
n
indicator that you should be using that schwartz thang.
-=- James Mastros
--
The most beautiful thing we can experience is the mysterious. It is the
source of all true art and science. He to whom this emotion is a stranger,
who can no longer pause to wonder and stand wrapt in awe, is as
Then again, if you think of objects (in the OO sense) as doing things, then
they normaly are the subject, and _not_ the indirect-object (in the english
sense).
(Note, BTW, that both my german and my lingustics aren't so hot.)
-=- James Mastros
--
The most beautiful thing we can experi
g out of his head
> and hiding behind the bookcase)
That's a really wierd image. Twisted, even.
-=- James Mastros
--
The most beautiful thing we can experience is the mysterious. It is the
source of all true art and science. He to whom this emotion is a stranger,
who can no longer pa
] elem, and extract the ->[1] elem. Thus, it might not be as
effecent as a hand-crafted schwartzian, but will be at least as efficent as
a naieve straight sort (except in pathalogical cases, like tsort((^_),
(^_<=>^_), @list)).
-=- James Mastros
--
The most beautiful thing we c
t;sub {}"s.)
Indeed,
map $_->[0], sort {&$sort($a->[1], $b->[1])} map [$_, &$attrib($_)], @list;
does what I intendeded. (Where ex $sort = sub {$_[0] cmp $_[1]}, and
$attrib = sub {lc $_}.) (Of course, this doesn't always use the optimal
form.)
-=- James Mastr
t; is immediate).
I'm fond of post, myself. Simply means "subsequent to", literaly (m-w.com,
post-, 2a. Yes, I'm anal sometimes.) "Always" makes me say "but when", and
"later" seems like the wrong part-of-speech to me.
-=- James Mastros
--
hat there would be a "invalid" marker of some sort.
It's neccessary (I think) for a pool, which I assumed. Bad James, bad.
-=- James Mastros
--
"All I really want is somebody to curl up with and pretend the world is a
safe place."
AIM: theorbtwo homepage: http://www.rtweb.net/theorb/
tly GC.
3) Automatic -- Certian runtime events, not directly (or obviously) related
to the flow of execution, like when the number of SVs created or the
amount of memory allocated since the last GC run exced a certian critical
value.
(I /think/ a dictionary would agree with me, but I'm not about to get pissy
and look them up.)
I was saying that we should do 1 and 3, but not 2.
-=- James Mastros
On Wed, Feb 14, 2001 at 09:59:31AM -0500, John Porter wrote:
> James Mastros wrote:
> > I'd think that an extension to delete is in order here. Basicly, delete
> > should DESTROY the arg, change it's value to undef,...
> Huh? What delete are you thinking of? This is
with a message about ``This object was already
> DESTROYed.''.
I think an ordinary "attempt to dereference undef" will work.
-=- James Mastros
--
"All I really want is somebody to curl up with and pretend the world is a
safe place."
AIM: theorbtwo homepage: http://www.rtweb.net/theorb/
On Tue, Feb 13, 2001 at 01:09:11PM -0500, John Porter wrote:
> > James Mastros wrote:
> > >"It isn't possible to AUTOLOAD DESTROY." --perlmem(6)
[Note: that's a hypothetical quote.]
> I'm not sure what that means. Certainly AUTOLOAD gets
> called
uctor)
Fiat?
It's pretty hard (for me) to think of when you'd want an AUTOLOADed DESTROY,
since if you create /any/ objects of the class, DESTROY will be called.
"It isn't possible to AUTOLOAD DESTROY." --perlmem(6)
-=- James Mastros
--
"All I really want is so
(cond) { somthing } }.
CATCH is just shorthand.
> - What's the return value? With RFC 88 you can say:
The return value is undef (or empty-list) until you hit a return statement.
If the code dies before returning, then it stays undef/() unless somthing
run after that (IE a CATCH/POS
On Mon, Feb 12, 2001 at 06:56:47PM -0300, Branden wrote:
> James Mastros wrote:
> > magical "install" script in them that knows how to do special things with
> > files in that directory (like set up symlinks from the normal man dirs).
>
> That probably should be
them that knows how to do special things with
files in that directory (like set up symlinks from the normal man dirs).
BTW, this plan would make it painful to do with perl5 setups, since they
commonly have odd dir structures.
-=- James Mastros
--
"All I really want is somebody to cur
sumers, assumedly)
licenced code from RSA. However, it shouldn't be a problem, since RSA's
pattent (in the US, anyway, and I don't think they pattented anywhere else)
has timed out.
-=- James Mastros
--
"All I really want is somebody to curl up with and pretend the world
No | Yes |
No. (Source packages are signed, though.) (At present, feature is planned
for future, and shouldn't be all that hard.)
-=- James Mastros
--
"All I really want is somebody to curl up with and pretend the world is a
safe place."
AIM: theorbtwo homepage: http://www.rtweb.net/theorb/
On Mon, Feb 05, 2001 at 08:43:02PM +0100, [EMAIL PROTECTED] wrote:
> On Mon, Feb 05, 2001 at 11:46:48AM -0500, James Mastros wrote:
> > By the time you get to the last line, you've already forgoten WTF you named
> > the return variable.
> Eh, I don't think that b
ormation
on scopes that caller doesn't (IE any scope not a do, require, eval, or
sub-call.)
-=- James Mastros
--
"My country 'tis of thee, of y'all i'm rappin'! Lan where my brothers
fought, land where our King was shot -- from every building top, le
it's independent of the sub's name. I wish this could be
> extended to doing recursive calls without having to say the subs own
> name, again.
I agree, making the magic variable be the name of the sub is a bad idea.
Your idea for a name for the currently executing sub is interesting, I
thin
ffer is two magic values, $^R and @^R. And, as
sombodyoranother pointed out, @^R can't be a real array, only a list. (I
don't think that will be a problem, though.)
> [stuff about manual vs. automatic return-stack elminition]
Yeah, you're probably right. But return-as-assignment
On Sun, Feb 04, 2001 at 05:30:59PM +0100, Johan Vromans wrote:
> James Mastros <[EMAIL PROTECTED]> writes:
> > And I always hated that about VB and Pascal -- you can assign to the magic
> > variable, but can't modify it.
>
> That was before the invention of a
he
difference between an alias and an automagicly dereferenced ref? If
nothing, why do we claim to never autoderef?) Is assigning to @__ the same
as assigning to @{$__}? Nope. Does @$__ have any meaning if $__ is an
alias, not a reference? Nope.
I'm quickly getting more confused here t
contain two
consecutive colons. (or "'"s, but that's going to be thrown out, I assume).
-=- James Mastros
--
"My country 'tis of thee, of y'all i'm rappin'! Lan where my brothers
fought, land where our King was shot -- from every building
#x27;s SysV IPC scheme into perl. (And I
don't even know what XPG4 is.)
Speaking of contract names, is Damien about?
-=- James Mastros
--
"My country 'tis of thee, of y'all i'm rappin'! Lan where my brothers
fought, land where our King was shot -- from eve
AC address of
the network card, and some other random stuff).
I think the current method is probably best for us.
-=- James Mastros
--
"My country 'tis of thee, of y'all i'm rappin'! Lan where my brothers
fought, land where our King was shot -- from every buildi
't modify it. And if you try, you don't error, you
recruse. And perl will happily recruse until you run out of memory, and VB
will give a stack overflow, and take down the IDE and your code unless
you're careful.
-=- James Mastros
--
"My country 'tis of thee, of y
s result slightly differently is not "not
keeping perl perl", nor is it not keeping time time; changing time() such
that it did somthing radicly different (like returning time-of-day instead)
would be changing it's soul.
And I don't think we should be keeping code-level compatablit
change the meaning of time() slightly without changing to a
different function name? Yes, it will silently break some existing code,
but that's OK -- remember, 90% with traslation, 75% without. being in that
middle 15% isn't a bad thing.
-=- James Mastros
--
"My country
ns. I
personaly would prefer to see units of seconds, a basepoint of 1/1/1970, and
resolution and accuracy best-reasonably-available.)
If you really want time() to do what it did before, you can always say:
sub time {int (CORE::time()) + };
Indeed, a perl5::time module that does exactly that mi
From: "Nathan Wiger" <[EMAIL PROTECTED]>
Sent: Friday, September 29, 2000 12:51 AM
> James Mastros wrote:
> > As far as setting|getting, I'd like to make a simple proposal. Consider
it
> > an idea for whoever writes the RFC (I'm looking at you, Nat
the value of
$hash{elem}, not on the spot in the hash.
I don't know what a good syntax for the hash position would be. And I've
got other work to do now.
-=- James Mastros
Creating attributes:
--
-BEGIN GEEK CODE BLOCK-
Version: 3.1
GU>CS d->-- s-:- a20
strict
"taint"'. (in default strict set?)
Hm, this behavor would be equivlent to making "unsafe" errors normal:
'no strict "taint"' == 'no taint'
'use strict "taint"' == 'use taint'
'use warnings "taint"' == 'use taint warnings'
(You'd have to put the warnings/errors about 'no taint' in the 'notaint'
set.)
-=- James Mastros
From: "Adam Turoff" <[EMAIL PROTECTED]>
> On Wed, Sep 27, 2000 at 12:09:20PM -0400, James Mastros wrote:
> > Really, I don't see why we can't
> > just have a 'use taint' and 'no taint' pargma.
>
> Because taint mode needs to
can run freely in the end-user's account. Think
cgi_wrapper without spawning a new interpreter.
-=- James Mastros
--
-BEGIN GEEK CODE BLOCK-
Version: 3.1
GU>CS d->-- s-:- a20 C++ UL+++@ P+++>+ L++@ E-() N o? K? w@ M-- !V
PS++ PE Y+ PGP(-) t++@ 5+ X+++ R+ tv+ b+++ DI+ D+ G e>++ h! r- y?
--END GEEK CODE BLOCK--
ly get
the location of the AUTOLOADER sub and not where the sub being autoloaded
was acatualy written.
Most of the rest would require siginificant overhead on all programs that
might get debugged (the debugger is a module; you don't necessarly have to
start it from the commandline). Us
From: "Nathan Wiger" <[EMAIL PROTECTED]>
To: "James Mastros" <[EMAIL PROTECTED]>
Sent: Thursday, September 14, 2000 5:32 PM
Subject: Re: RFCs up for adoption, and a proto-RFC
> James Mastros wrote:
> > RFC 163: Automatic accessors for hash-based obj
27;s being
called at compiletime or runtime.
Please CC me on any replies; I'm probably going to unsubscribe from
perl6-language-*.
-=- James Mastros
1 - 100 of 112 matches
Mail list logo