ake a moment to sift
through the changes. I vote to never see those diff emails ever again. In
fact, if the diffs are brought back, I'll just subscribe to the commit feed
and skip the email notice all together.
-Jason
on what task is at hand,
this may be of no use. I am finishing a masters in NLP and after all this
work, p6 grammars wouldn't have helped much.
-Jason "s1n" Switzer
edia.org/wiki/Interface_(Java)#Defining_an_interface
Just an idea.
-Jason "s1n" Switzer
, something similar to POE, or something
that emulates Erlangs process management.
If you keep Buk's bullet points and give me a minimalistic interface to
threads/shared memory, then it would allow me to create whatever wacky
threading/shared memory model I can imagine. I think that's better than
doing something that sounds dangerously similar to Java's RMI.
-Jason "s1n" Switzer
e largest represented
unit.
-Jason "s1n" Switzer
ld be removed. I'm all ears though
if someone knows of a reason why they're more useful than onerous.
-Jason "s1n" Switzer
re incapable of displaying italics so underlining was taught as a
replacement, though italics are/were considered the professional format. I
somehow doubt that Markdown chose the _ for italics for that reason, though
I will say that wayland's suggestion just makes more sense.
-Jason "s1n" Switzer
On Mon, Dec 28, 2009 at 9:59 PM, Jason wrote:
>
>
> *Connected by MOTOBLUR™ on T-Mobile
> *
>
My phone accidentally sent an empty reply to this. What I was supposed to
reply with was information regarding the built-in Rakudo REPL. You can see
it in action here:
http://perl6adven
Connected by MOTOBLUR™ on T-Mobile
-Original message-
From: Juan Madrigal
To: perl6-language@perl.org
Sent: Tue, 29 Dec 2009 03:41:50 GMT+00:00
Subject: Interactive Perl 6 shell
Does Perl6/Rakudo have an interactive perl shell like ruby does with irb?
http://en.wikipedia.org/wiki/Inte
ilar to perl5,
GCC, python, and lots of other compilers/interpreters.
-Jason "s1n" Switzer
Since I don't know anything about nuclear power plants, I think the BikeShed
should be painted blue and called "Rakudo Whatever" or just "Rakudo".
-Jason "s1n" Switzer
BEGIN:VCALENDAR
PRODID:-//Google Inc//Google Calendar 70.9054//EN
VERSION:2.0
CALSCALE:GREGORIAN
METHOD:REQUEST
BEGIN:VEVENT
DTSTART:20090610T00Z
DTEND:20090610T03Z
DTSTAMP:20090605T035152Z
ORGANIZER;CN=jason switzer:mailto:jswit...@gmail.com
UID:g3rsts66avsaacp817n7ri1...@google.com
BEGIN:VCALENDAR
PRODID:-//Google Inc//Google Calendar 70.9054//EN
VERSION:2.0
CALSCALE:GREGORIAN
METHOD:REQUEST
BEGIN:VEVENT
DTSTART:20090610T00Z
DTEND:20090610T03Z
DTSTAMP:20090605T035153Z
ORGANIZER;CN=jason switzer:mailto:jswit...@gmail.com
UID:g3rsts66avsaacp817n7ri1...@google.com
I would give any consideration to would be to extend the
versioning metadata to allow for the user to define new metadata. That
sounds too similar to the goals of XML, but it would at least allow the
community to define what metadata is important.
Some things are best left unsaid.
-Jason "s1n" Switzer
mmars.
That may be a bit naive, but someone pointed this section out to me and it
raised a ton of questions.
-Jason "s1n" Switzer
:
http://images.google.com/images?gbv=2&hl=en&q=kitchen+sink
-Jason "s1n" Switzer
suppose could turn into an evil pragma, if we
> + try to translate it at all. (Frees up * twigil for $*FOO syntax.)
I'm not even sure this makes sense to me. Is this saying that $* and $# are
largely not in use anymore (in perl6)?
-Jason "s1n" Switzer
s my crappy ok()
That's just an example to show that the language could provide a basic
version that is extensible with various implementations and various
compilers such that I don't have to write constantly unique test names (or
poorly identified names) and still only have to write a test once.
-Jason "s1n" Switzer
While I realize this is just an example, adverbs that apply to a
specific emitter would not be my preference. Extensible emitters would allow
integrators the opportunity to mix perl6 tests in with perl5 tests and xUnit
tests (for easily integrated test reports).
-Jason "s1n" Switzer
ay not integrate
well. It would be nice if the spec, if added, would allow flexibility in
this realm. I would actually like to see a flexible system that allowed me
to define a new emitter, say for the cases where you want to integrate perl6
testing into an existing testing framework (think automated builds and
tests).
-Jason "s1n" Switzer
pugs specific,
which is ironic. What are all the references to Pugs::Internals and
pugs_internals_m:perl5? Is rx:Perl5 and rd:P5 valid perl6?
I'm skeptical of the this idea unless someone can convince me otherwise.
-Jason "s1n" Switzer
On Mon, Jan 12, 2009 at 6:26 PM, Ovid
wrote:
> - Original Message
>
> > From: jason switzer
>
> > If we wanted language dependent version, use :leading, :trailing, and
> :both.
> > That will require each implementation properly handle the language
> >
-e 'my $foo = '\''foo'\''; say '\''{'\'' ~ $foo ~ '\''}'\'' '
{foo}
Notice the overly redundant single-quotes; in fact, all of those quotes are
single quotes.
-Jason "s1n" Switzer
verywhere.
If we wanted language dependent version, use :leading, :trailing, and :both.
That will require each implementation properly handle the language
variations.
By the way, good work on this. Everyone loves useful string functions.
-Jason "s1n" Switzer
pod2html and for streamlined perl6 implementations to skip things like
--doc.
-Jason "s1n" Switzer
On Mon, Dec 15, 2008 at 6:59 PM, Leon Timmermans wrote:
> On Mon, Dec 15, 2008 at 6:42 PM, jason switzer wrote:
> > It's lazy and kinda cheating, but for small simple tasks, it gets the job
> > done. I'm not up to speed with the IO spec, but a sort of auto-slurp
> &
gt; provide the syntatic sugar that makes specifying a location look like
> specifying a directory natively, eg.
> use IO::Windows;
> my Location $x .= new(:OSpath);
> whilst for linux it would be
> use IO::Linux;
> my Location $x .=new(:OSpath);
This looks like a good start to the whole file path issue discussed above
but gets too OS specific. I think things like FUSE and Samba on linux could
throw a real curveball into that but I'm not sure how much latitude the
kernel gives file systems and userspace applications the power to change the
default naming scheme (i.e. if / can be changed to \).
-Jason "s1n" Switzer
It makes sense to me to go with option 1; you get what you ask for. It also
makes sense to make to not use magical implied numbers, such as negatives,
to accomplish things that either ranges or whatever star can accomplish.
Just my 2 cents.
-Jason "s1n" Switzer
On Tue, Sep 23, 2008
Says Dave Mitchell:
> Closures ... can also be dangerous and counter-intuitive, espcially to
> the uninitiated. For example, how many people could say what the
> following should output, with and without $x commented out, and why:
>
> {
> my $x = "bar";
> sub foo {
> # $x # <-
On (03 May 2001 10:23:15 +0300) you wrote:
> Michael Schwern:
> >
> > Would be neat if: my($first) = grep {...} @list; knew to stop itself, yes.
> >
> > It also reminds me of mjd's mention of: my($first) = sort {...} @list;
> > being O(n) if Perl were really Lazy.
>
> But it would need a
> So you can say
>
> use Memoize;
> # ...
> memoize 'f';
> @sorted = sort { my_compare(f($a),f($b)) } @unsorted
>
> to get a lot of the effect of the S word.
Yes, and of course the inline version of this technique is also
common:
@sorted = sort { my $ac = $cache{$a} ||= f($a);
Bart Lateur:
> >If there are no objections, I will freeze this in twenty-four hours.
>
> Oh, I have a small one: I feel that this pseudo-random salt should NOT
> affect the standard random generator. I'll clarify: by default, if you
> feed the pseudo-random generator with a certain number, you'l
ot
share pads, the code will continue to work.
So your proposal can be saved, but it needs to be fixed.
Mark-Jason Dominus [EMAIL PROTECTED]
I am boycotting Amazon. See http://www.plover.com/~mjd/amazon.html for details.
ever.
The programmer can also examine the occurrences of 'perl5_eval' in the
source code to decide whether they can be converted immediately to
plain 'eval'.
Once all the appearances of perl5_eval have been replaced, the
translator is no longer needed.
Mark-Jason Dominus
> eval should stay eval.
Yes, and this is the way to do that.
When you translate a script, the translator should translate things so
that they have the same meanings as they did before. If it doesn't
also translate eval, then your Perl 5 scripts will be using the Perl 6
eval, which isn't wha
> > One could for example have a pragma to *really* tag variables
> > lexically to be expanded within singlequotes.
Or a pragma that simply changes the semantics of q{...} so that it has
the proposed feature for the rest of the scope of the current block.
The perl 5 -> perl 6 translator should replace calls to 'eval' with
calls to 'perl5_eval', which will recursively call the 5->6 translator
to translate the eval'ed string into perl 6, and will then eval the
result.
Mark-Jason Dominus
> seconded by Mark-Jason Dominus <[EMAIL PROTECTED]>
Except that I don't think adding this feature to the existing q{...}
is a good idea. If I had to vote on your proposal, I would instantaly
vote against it. I think you should have invented a new operator or a
pragma or something.
> =head1 TITLE
>
> crypt() default salt
>
> =head1 VERSION
>
> Maintainer: Mark Dominus <[EMAIL PROTECTED]>
> Date: 11 Sep 2000
> Last Modified: 13 Sep 2000
> Mailing List: [EMAIL PROTECTED]
> Number: 208
> Version: 2
> Status: Developing
If there are no objections, I will freez
> This reminds me of a related but rather opposite desire I have had
> more than once: a quotish context that would be otherwise like q() but
> with some minimal extra typing I could mark a scalar or an array to be
> expanded as in qq().
I have wanted that also, although I don't remember why ju
> You talked about Good Typing at YAPC, but I missed it. There's a
> discussion of typing on perl6-language. Do you have notes or a
> redux of your talk available to inform this debate?
http://www.plover.com/~mjd/perl/yak/typing/TABLE_OF_CONTENTS.html
http://www.plover.com/~mjd/perl/yak/typing
g
This warns you that C<"[EMAIL PROTECTED]"> is going to turn into
C if you don't backslash the C<@>.
See L<http://www.plover.com/~mjd/perl/at-error.html> for more details
about the history here.
Mark-Jason Dominus
locales, not to mention to be consistent with the
perl docs themselves.
There is no convenient way to imitate this functionality in Perl while
supporting locales. There should be.
Jason Elbaum
[EMAIL PROTECTED]
application. Perl has two equality comparison operators and people
aready complain that that is too many.
Mark-Jason Dominus [EMAIL PROTECTED]
I am boycotting Amazon. See http://www.plover.com/~mjd/amazon.html for details.
Each process has one real UID, and only one, so a
global variable for $< is perfectly OK.
$_ is in a class by itself.
Summary of manifesto: Global variables must be expunged.
Replacing the old rotten global variables with new rotten global
variables is not enough of an improvement.
Mark-Jas
45 matches
Mail list logo
