-- a
little playful fun.
Would your proposal imply that I would not be able to open this file any
more without resorting to "tricks" such as sysopen or './http://blabla'?
Just wondering.
Cheers,
Philip
--
Philip Newton <[EMAIL PROTECTED]>
kind of like locale, even if you don't call it that. (And IIRC, the
mapping of uppercase(LATIN LETTER SHARP S) to "SS" is also a special case
for German.)
Cheers,
Philip
--
Philip Newton <[EMAIL PROTECTED]>
ssed in p5p several times. There was even
code posted to p5p at one point that would introduce the operator
(spelled, I believe, |||) into the sources.
Cheers,
Philip
--
Philip Newton <[EMAIL PROTECTED]>
I appreciate copies of replies to my messages to Perl6 lists.
r
numbers automatically fail-over to bigint, otherwise, for portability, one
would probably be better off using bigints all the time.
Cheers,
Philip
--
Philip Newton <[EMAIL PROTECTED]>
I appreciate copies of replies to messages I sent to Perl 6 lists.
ith ASCII (for example, JIS has a Yen
sign in place of the backslash, I believe). Even if we ignore language-
specific variants of ISO 646; I don't know whether they're still in use
anywhere, but if they are, then { | } [ \ ] ~ are all out, and probably
a couple of others, too (@?).
C
7;m misusing UTF-32. (UTF-8 is variable-width--is UTF-32?)
No. UTF-32 is always 4 bytes AIUI. UTF-8 is variable (1..4) and so is
UTF-16 (either 2 or 4, though 4 bytes are needed only for characters >
U+, i.e. outside the BMP or Basic Multilingual Plane).
Cheers,
Philip
--
Philip Newton &l
to U+. However, UTF-8 is longer than UTF-16 for
characters gt U+07FF (but catches up again for U+1 to U+10: both
encodings need four bytes for characters in that range because of
UTF-16's surrogate encoding).
Cheers,
Philip
--
Philip Newton <[EMAIL PROTECTED]>
On 14 Nov 2000, Chaim Frenkel wrote:
> Did I miss something? I didn't see any discussion. Was this off-line?
No, on perl6-announce and perl6-internals.
Cheers,
Philip
--
Philip Newton <[EMAIL PROTECTED]>
it? Since "use" includes a "require". (On the other
hand, it's a require in a BEGIN block, so that may not be a problem
after all.)
Cheers,
Philip
--
Philip Newton <[EMAIL PROTECTED]>
ot;, we get something like:
>
> @foo wa kaite kudasai;
^^
Shouldn't that rather be "wo"?
Cheers,
Philip
--
Philip Newton <[EMAIL PROTECTED]>
t;
> Nah. Only those newbies that don't speak Japanese. If we wanted to keep the
> newbies out we'd write perl 6 in INTERCAL. :-P
I don't think Claudio Calvelli would mind (though I don't know whether he
speaks Japanese).
Cheers,
Philip
--
Philip Newton <[EMAIL PROTECTED]>
On Thu, 19 Oct 2000, J. David Blackstone wrote:
> [And now they're keeping the newbies locked out by doing all
> development work in Japanese.]
Well, we might get lots of developers recruited from the Ruby camp ;)
Cheers,
Philip
--
Philip Newton <[EMAIL PROTECTED]>
third @foo" to me.)
> That brings up two questions:
> - what's the ordinal for 'zeroth'
Presumably, dai-rei or dai-zero. (With "zero" being pronounced zeh-ro and
not zee-roh.)
> - are lists 'long-flat-objects' or 'tall-cylindrical-objects'
> or 'short-fat-cylindrical-objects'?
>
> Inquiring gaijin want to know! :-)
;)
Cheers,
Philip
--
Philip Newton <[EMAIL PROTECTED]>
front.
No, IMO they'd still need to go at the end. Now, whether "the end" is the
left, right, or bottom depends on which way you're righting. (I've never
come across Japanese being written from bottom to top.)
Cheers,
Philip
--
Philip Newton <[EMAIL PROTECTED]>
ber like a PIN number or an LCD display? [Someone once
mentioned they had even heard of "personal PIN number"... eek.]
--
Philip Newton <[EMAIL PROTECTED]>
On 5 Oct 2000, at 13:44, Dan Sugalski wrote:
> At 06:19 PM 10/5/00 +0200, Philip Newton wrote:
> >On 2 Oct 2000, at 16:14, Dan Sugalski wrote:
> >
> > > I'll have to go pick that up on Thursday and add it to the Darned Big Pile
> > > of books I need to re
; is the bible of the genre.
>
> I'll have to go pick that up on Thursday and add it to the Darned Big Pile
> of books I need to read.
Funny how everyone seems to have on of those. (Most of the books
on my DBP I haven't even bought yet.)
Cheers,
Philip
--
Philip Newton <[EMAIL PROTECTED]>
be kept in mind.
Cheers,
Philip
--
Philip Newton <[EMAIL PROTECTED]>
I appreciate copies of replies to my messages to Perl6 lists.
derstand/patch/correct multiple markup formats.
I believe Perl can still embed raw *roff. IIRC, in Perl 1, POD hadn't
been invented, and Larry used raw *roff inside Perl code. However, I
don't think this practice is encouraged these days ;)
Cheers,
Philip
--
Philip Newton <[EMAIL
pod
>
> =cut
>
> it can certainly be made to skip between:
>
>
>
Skipping between
=pod
and
=cut
is a lot easier than between
and
when you are reading a line at a time; you can simply strcmp them
and not have to worry about what happens if there's other stu
d set of documentation that is of no use to anyone." I think
it's more likely that switching to an XML docset produces very little
documentation, and what there is will be of widely varying quality. Not
everyone will want to expend the effort involved to plan out, carefully,
their documen
On 28 Sep 2000, at 21:36, iain truskett wrote:
> * Philip Newton ([EMAIL PROTECTED]) [28 Sep 2000 21:19]:
> > On 27 Sep 2000, at 23:48, iain truskett wrote:
>
> > > So surely you'd want %HTTP (the input headers) to also be an array
> > > rather than a hash, s
@out = header (%temp = unheader @in);
If you just take unheader's output and feed it to header, the order will
be the same. Thanks for bearing with me ;)
Cheers,
Philip
--
Philip Newton <[EMAIL PROTECTED]>
s, conversion to lowercase, and so forth.
> So, this call:
>
>@out = header unheader @in;
>
> Should result in C<@out> being exactly equivalent to C<@in>.
It cannot, of course, since the order of hash keys obtained by flattening
the hash is not necessarily the same
On 27 Sep 2000, at 23:48, iain truskett wrote:
> So surely you'd want %HTTP (the input headers) to also be an array
> rather than a hash, since they'd be required in order as well?
I don't care, because I don't work with this much. And I don't know
whether I'd need to bear in mind the protocol
Better to have something that's either (a) pluggable without
having to replace all of Perl, or (b) header-agnostic, so you have to
specify your own ordering -- which also means you *can* specify your own
ordering.
Cheers,
philip
--
Philip Newton <[EMAIL PROTECTED]>
big arrow, which is equivalent to - "name" and a
comma. Fortunately, - "string" doesn't convert "string" to a number (0)
and then apply negation but results in "-string" (`perldoc perlop` says:
"If the operand is an identifier, a string consisting of a minus sign
concatenated with the identifier is returned. [...] One effect of these
rules is that `-bareword' is equivalent to `"-bareword"'."
Cheers,
Philip
--
Philip Newton <[EMAIL PROTECTED]>
On 26 Sep 2000, Johan Vromans wrote:
> Philip Newton <[EMAIL PROTECTED]> writes:
>
> > so fewer "cluttering"
> > parentheses are needed to make things readable while still being correct.
>
> Since when do parentheses make things less readable?
Each par
On 26 Sep 2000, Johan Vromans wrote:
> Philip Newton <[EMAIL PROTECTED]> writes:
>
> > so fewer "cluttering"
> > parentheses are needed to make things readable while still being correct.
>
> By the same reasoning, you can reduce the use of curlie
On 25 Sep 2000, at 13:05, Ben Tilly wrote:
> David Grove wrote:
>
> > However, I am speaking in generalities. If it's
> > perl, it's redistributable. If it isn't redistributable, it isn't
> > perl. This include both binaries and source, since binaries are only
> > translations of source into anot
On 25 Sep 2000, at 10:03, Ben Tilly wrote:
> I think David is confused about this situation, but what he
> said is not entirely false. Anyone who wants can get Perl,
> make changes under the GPL, and release the hacked up version
> under the GPL. You would now have a GPL-only fork of Perl
> whi
::Blurf'->meth().)
Cheers,
Philip
--
Philip Newton <[EMAIL PROTECTED]>
escape sequences cannot be defined
beforehand).
Cheers,
Philip
--
Philip Newton <[EMAIL PROTECTED]>
more tightly than || or &&), so fewer "cluttering"
parentheses are needed to make things readable while still being correct.
Cheers,
Philip
--
Philip Newton <[EMAIL PROTECTED]>
On Thu, 21 Sep 2000, Tom Christiansen wrote:
> =item perl6storm #0035
>
> Make A->B place A in string context, like => does.
> That way no A()->B naughtiness.
While still allowing explicit A()->B?
Cheers,
Philip
--
Philip Newton <[EMAIL PROTECTED]>
wondering whether perl was installed on a machine
and typed 'perl' to see -- and "nothing happened". (I suppose either of
`which perl` or `perl -v` would be a better way to find out, but still.)
Having Perl tell me 'this is perl5.7.0\n> ' or similar would have be
anal python folks.
What are defaults, in this context? Things like abs taking $_ if no
variable is specified? Or localtime taking time()? Or what?
Cheers,
Philip
--
Philip Newton <[EMAIL PROTECTED]>
ng $seen{$word}++ turn $seen{$word} to undef is bad, if (undef)++
assumes NULL semantics everywhere, hence "one more than unknown" = "still
unknown".
Cheers,
Philip
--
Philip Newton <[EMAIL PROTECTED]>
nicer than
$seen{$word} = (exists $seen{$word}) ? 1 : $seen{$word} + 1;
or
if(defined($seen{$word})) { $seen{$word}++ } else { $seen{$word} = 1 }
or similar.
Cheers,
Philip
--
Philip Newton <[EMAIL PROTECTED]>
On 15 Sep 2000, at 11:25, Steve Fink wrote:
> Does it strike anyone else as odd that 'foo\\bar' eq 'foo\bar'?
While 'foo\\' ne 'foo\' :-) (specifically, the former is not a syntax error
:-)
Cheers,
Philip
heers,
Philip
--
Philip Newton <[EMAIL PROTECTED]>
t might be interesting to reread the whole
paragraph.)
Cheers,
Philip
--
Philip Newton <[EMAIL PROTECTED]>
On 14 Sep 2000, at 14:18, Nathan Wiger wrote:
> Before you balk at #1 in favor of religious flexibility, please consider
> how unmaintainable Perl code would be if @ARGV, or $AUTOLOAD, or STDERR,
> or @INC, or chomp(), or split(), or any other widely-used variable or
> function was renameable. If
On 14 Sep 2000, at 21:06, Glenn Linderman wrote:
> I _like_ the conceptual idea, here. But I think we need a different kind of
> quoting, not extend single quote semantics. Single quote semantics are really,
> really, good for exact quoting. I'm sure you (since you mention VMS) find single
> q
On 15 Sep 2000, at 1:10, Perl6 RFC Librarian wrote:
> With this proposal, the scalar C<$filename> can be tagged to be interpolated
> by the C<\I...\E> pair and the double quotish context replaced by single
> quotish context resulting in the following:
Definitely with this change, you should incl
, there's no guarantee that %ld is the correct format to print it out.
Might as well be %llu or %d as %ld.
Maybe POSIX makes more guarantees.
Cheers,
Philip
--
Philip Newton <[EMAIL PROTECTED]>
or in a list context, does
"C<< (<>); >>" break, or does it mean something like "C>> @_ = <>; >>" ?
I especially wonder about your c<;> escape.
> =head2 3: For Functions In General
>
> "C;", "C", and many others could use C<$_>.
Er, they already do. man perlfunc, and/or see my list above.
Cheers,
Philip
--
Philip Newton <[EMAIL PROTECTED]>
t;Press any key" and wasting the
> input.
I suggest again:
s/"<>"/"C<< <> >>"/g; s/C<$_ = > <>/C<< $_ = <> >>/;
Cheers,
Philip
--
Philip Newton <[EMAIL PROTECTED]>
>". I can't yet think of code that this extension would break.
And by the way, this would break code that uses <>; to discard a line of
input but wishes to preserve $_. (For example: print "Press Enter to
continue\n"; ; print "Continuing to operate on '$_'\n";)
Cheers,
Philip
--
Philip Newton <[EMAIL PROTECTED]>
On 31 Aug 2000, Perl6 RFC Librarian wrote:
>my format $FILE_FORMAT =
> @<<<<<<<<<<<<<: @<<<<<<<<
> $name, $ssn
> .
>
> Then this is even less different and scary. Get rid of that C and
> it's Perl 5.
s/that C/that C and the dollar sign/;
Cheers,
Philip
--
Philip Newton <[EMAIL PROTECTED]>
On 28 Aug 2000, Perl6 RFC Librarian wrote:
> This and other RFCs are available on the web at
> http://dev.perl.org/rfc/
>
> =head1 TITLE
>
> Remove mathematic and trigonomic functions from core binary
$RFC[155] =~ s/trigonomic/trigonometric/g;
Cheers,
Philip
--
Phi
On Tue, 29 Aug 2000, Mark-Jason Dominus wrote:
> OK, I think this discussion should be closed.
I think the bit about "having a special array containing all captured
matches" might well still live on. The "counting" bit _per se_ is probably
fairly closed, though.
Ch
On 27 Aug 2000, Perl6 RFC Librarian wrote:
> With a here doc print <
ng out in the body of the document, makes indenting blocks of text
> difficult and causes errors and confusion.
s/verbatum/verbatim/;
Cheers,
Philip
--
Philip Newton <[EMAIL PROTECTED]>
I use in a script of mine is:
while ($string =~ /(\d\d)-(\d\d)-(\d\d)/g) {
($mo, $dy, $yr) = ($1, $2, $3);
}
Although this, of course, also requires that you know the number of
backreferences. Nicer would be to be able to assign from @matchdata or
something like that :)
Cheers,
Phi
stops working. I think the above method (having to add your own spaces, in
the exact number required at the moment) is too fragile.
Cheers,
Philip
--
Philip Newton <[EMAIL PROTECTED]>
ikely that there will
be any in the near future, but that there is provision for them.
The IERS (International Earth Rotation Service) monitors things and sends
out a bulletin twice a year, saying whether there will, or will not, be a
leap second on 30 June or 31 December (and which sign it will have if
there is one).
Cheers,
Philip
--
Philip Newton <[EMAIL PROTECTED]>
ing loop round a m//g. But this all seams rather messy.
$count = () = $variable =~ m/foo/g;
The () puts the match into list context (so the matches themselves are
returned), and that list assignment evaluated in scalar context, giving
the number of values assigned to the list.
Cheers,
Philip
-
58 matches
Mail list logo
