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-langu...@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
# New Ticket Created by "jason switzer"
# Please include the string: [perl #68996]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=68996 >
(12:56:30) s1n: rakudo: class A { has $.foo = 'bar'; mul
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
ch as Patrick Michaud (the Ra
kudo pumpking)\, are encouraged to attend. There's obviously lots to talk a
bout this month (post-YAPC\, pre-OSCON)\, so I look meeting with everyone a
gain.\n\nAs always\, everyone is invited to come and have a good time. See
you there!\n\n-Jason "s1n"
# New Ticket Created by "jason switzer"
# Please include the string: [perl #67374]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=67374 >
(21:38:19) s1n: rakudo: die
(21:38:24) p6eval: rakudo 70bfd5: OUTPUT«
# New Ticket Created by "jason switzer"
# Please include the string: [perl #67372]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=67372 >
(21:42:03) s1n: rakudo: warn
(21:42:06) p6eval: rakudo 70bfd5: O
# New Ticket Created by "jason switzer"
# Please include the string: [perl #67364]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=67364 >
Recent changes to replace trait_auxiliary: with trait_mod: started
cau
# New Ticket Created by "jason switzer"
# Please include the string: [perl #66822]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=66822 >
(2:34:19 PM) s1n_yapc: rakudo: sub foo($opt?, $other) { say &quo
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
# New Ticket Created by "jason switzer"
# Please include the string: [perl #66006]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=66006 >
When a method is called without using one of the available signatures,
# New Ticket Created by "jason switzer"
# Please include the string: [perl #65346]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=65346 >
I ran into a bug where I couldn't refer to 'self' wh
# New Ticket Created by "jason switzer"
# Please include the string: [perl #64448]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=64448 >
When moving outside of the rakudo git directory, the execution of the
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
# New Ticket Created by "jason switzer"
# Please include the string: [perl #62178]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=62178 >
When mixing gather with a while loop, only the last element tested
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
# New Ticket Created by "jason switzer"
# Please include the string: [perl #59222]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=59222 >
This patch adds radix notation (:\d<...>) to the string-to-number
# New Ticket Created by "jason switzer"
# Please include the string: [perl #58560]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=58560 >
The List !flatten method does not properly recurse into references.
# New Ticket Created by "jason switzer"
# Please include the string: [perl #58094]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=58094 >
The attached patch adds a few more test files to the spectest_regressio
# New Ticket Created by "jason switzer"
# Please include the string: [perl #57776]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=57776 >
[EMAIL PROTECTED] perl6 $ gdb ./perl6
GNU gdb 6.8
Copyright (C) 2008
# New Ticket Created by "jason switzer"
# Please include the string: [perl #57522]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=57522 >
The test harness used the default verbosity mode provided by TAP::Harne
# New Ticket Created by "jason switzer"
# Please include the string: [perl #57444]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=57444 >
Recent changes to the S29-trig tests have them properly fudged and
# New Ticket Created by "jason switzer"
# Please include the string: [perl #56712]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=56712 >
When trying to use the --optimize flag, building perl6 causes parro
James Keenan wrote:
> (Coleoid: Does this update cause any problems for you on Win32 without
> ICU?)
No visible problems from prove and Configure. Output seems the same and
indicates success. Pasted in #parrot.
Trying to 'make', though, I've started emitting hundreds of 'warning: control
re
# New Ticket Created by "jason switzer"
# Please include the string: [perl #56660]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=56660 >
I found a case where my Rakudo test harness and the spectest_regression
I'm having this same issue with r24319, but the target name is now
pbc_to_exe. Same issue, though.
chromatic requested the contents of my pbc_to_exe.pir when I brought up
the issue on use.perl.org -- it is attached.
pbc_to_exe.pir
Description: Binary data
anyone done this before i figure out how to do it?
Many Thanks!
-jason gessner
[EMAIL PROTECTED]
# Dumping Core...
# '
# expected: 'ok 1
# ok 2
# ok 3
# '
# Looks like you failed 5 tests of 6.
The script in question is attached.
dynlexpad.t
Description: Binary data
I hope this helps! The make test passed everything, but this error
occurred while running make fulltest.
-jason gessner
[EMAIL PROTECTED]
is skip supposed to be case sensitive? is it Skip, skip or SKIP ?
TODO seems to be all caps.
-jason gessner
[EMAIL PROTECTED]
On Feb 19, 2005, at 8:48 PM, Andy Lester wrote:
The synopsis uses passive voice; <.> is called TAP.
Id turn that around.
TAP, the Test Anything Protoc
st::Harness!!!
-jason gessner
[EMAIL PROTECTED]
sults of those
assertions. Printing to STDERR/STDOUT, hijacking those and pretty
printing the
results is simply not enough in all cases. It is awesome in some cases. Just
not all.
sorry for the rant. I have seen an RT request for at least a data structure
returned for results. any movement on that?
-jason gessner
[EMAIL PROTECTED]
David Cantrell wrote:
Jason Gessner wrote:
Andy Lester wrote:
So it's sort of adding make functionality with prove. The way the check
is running in the patch, the only criteria for updating it is changes
in the .t file, but what if what you're updating is the source file?
Detecting a
Andy Lester wrote:
On Sun, Dec 12, 2004 at 12:24:26AM -0600, Jason Gessner ([EMAIL PROTECTED])
wrote:
This is not designed as a replacement for a cron'd prove. The way i see
it being used is in a terminal window adjacent to an editing session
while trying to nail down a problem.
So it&#
tests.
This is not designed as a replacement for a cron'd prove. The way i see
it being used is in a terminal window adjacent to an editing session
while trying to nail down a problem.
Thoughts?
-jason gessner
[EMAIL PROTECTED]
23a24
> my $session = 0;
42a44
> 'session
Hi,
On Wed, 8 Dec 2004 13:37:14 -0500, "Michael G Schwern"
<[EMAIL PROTECTED]> said:
> On Tue, Dec 07, 2004 at 07:21:09PM -0800, Jason Remillard wrote:
> > I ran the codestriker (http://codestriker.sourceforge.net/) test set
> > using Devel::Cover. The test
the script. I would be interested
in knowing if a cleaner way is possible, as this is kind of lame.
Thanks
Jason.
I'm writing automated tests for the example code in my book, which
will go into production early next month. I have the harness and test
apparatus all set up; I wrote a complete set of tests for chapter 6,
and I think I know how I want it done. But I need help writing the
tests themselves, becau
On Tue, Jul 15, 2003 at 10:15:57AM +0200, Leopold Toetsch wrote:
How is the described scheme supposed to work with JIT generated code ?
--
Jason
On Sun, Mar 23, 2003 at 03:54:21PM +0100, Leopold Toetsch wrote:
> Not really, but I don't see, how this set of macros would influence
> debugging negatively.
You can't step through the expanded code for a macro in the debugger.
--
Jason
On Fri, Mar 07, 2003 at 11:38:41PM +, Jason Gloudon wrote:
> # New Ticket Created by Jason Gloudon
> # Please include the string: [perl #21508]
> # in the subject line of all future correspondence about this issue.
> # http://rt.perl.org/rt2/Ticket/Display.html?id=21508 >
But with proper tail call optimization you'd only need *one*
> saveall. That's why it's an optimization.
Tail call optimization is a space (stack size) optimization. The scheme
definition only requires space efficiency. The time optimization is important
but a secondary consideration for the functional language folks.
--
Jason
On Wed, Feb 26, 2003 at 09:31:39AM -0800, Sean O'Rourke wrote:
> Dan -- you might be interested in
> http://www.usenix.org/events/javavm02/chen_m.html (if you have a USENIX
Research wants to be free:
http://www-hydra.stanford.edu/publications/JVM02.pdf
--
Jason
data.
It's not going to be very good if I compile code to pbc on an x86 where there
are about 3 usable registers and try to run it on any other CPU with a lot more
registers.
--
Jason
Dan Sugalski <[EMAIL PROTECTED]>:
> At 2:06 PM + 2/19/03, Peter Haworth wrote:
> >On Fri, 14 Feb 2003 15:56:25 -0500, Dan Sugalski wrote:
> >> I got clarification. The sequence is:
> >>
> >> 1) Search for method of the matching name in inheritance tree
> >> 2) if #1 fails, search for an AUTO
tor. Basically the entry points to basic
blocks are replaced with enternative calls so that the transition to compiled
basic blocks of ops code happens transparently to the interpreter.
--
Jason
can't do that for prederef in a multi-threaded process because prederef
stores the address of the registers in the interpreter structure in the
prederef data.
case PARROT_ARG_I:
pc_prederef[i] = (void *)&interpreter->ctx.int_reg.registers[pc[i]];
--
Jason
y good for a single interpreter.
--
Jason
preter->ctx.int_reg.registers[interpreter->code->base.data[offs+i]]
following the names you've used in previous mail.
Intersegment jumps may not work readily for all runloops, but I don't believe
that requires as big a change as you're suggesting.
--
Jason
nged and code_start would no
longer be correct.
--
Jason
; process, of all the modules.
Are you sure the swap space allocation isn't mostly attributable to the poor
locality in the Perl process's data structures ?
--
Jason
does not have to support making every instruction a safe
branch destination.
--
Jason
-contained inter-segment jump instruction.
Since the compiler knows when a branch is non-local it can always break a
non-local conditional branch into a conditional local branch to a non-local
branch instruction.
For example
if i, nonlocal
... not taken
can be expressed as
if i, TAKEN
... not taken
...
TAKEN: inter_jump nonlocal
--
Jason
s, that have specific entry points.
Maybe Dan could give us a hint about the closure/block/byte code segment
relationship.
--
Jason
rence may be deleted because you don't
know the side-effects of code that you're calling, so you would always have to
make sure it is anchored, and incur the overheads etc.
--
Jason
or and stick with the current stop
the world collector. Parrot's basic execution speed will be unchanged. By
trading heap size against frequency of collector runs, one could amortize the
cost of running the collector. Extension and core code programmers would never
have to think about the garbage collector in order to write correct code.
--
Jason
alk the hardware stack that's too costly to be
practical.
The best partial solution to early finalization is compile-time tracing of
possible references by the compiler which can explicitly generate the
appropriate DESTROY calls.
--
Jason
top)
-interpreter->lo_var_ptr = stacktop;
}
void
--
Jason
making it a core platform for parrot at this time.
--
Jason
On Fri, Nov 22, 2002 at 02:04:20PM +0100, Leopold Toetsch wrote:
> Parrot_sub_i_i {
> Parrot_binop_x_x s//sub/ s/<_N>//
> }
The only question I have is .. How am I supposed to read/translate the above ?
--
Jason
is out of
> range: 0x81c3e008
That in itself shouldn't have mattered (signed/unsigned) but this version does
fix the lexicals.t test failures.
--
Jason
/* cpu_dep.c
* Copyright: (When this is determined...it will go here)
* CVS Info
* $Id$
* Overview:
* CPU dependent
Indeed, if I try to use the debugger and "print list"
> while in list_new, I simply get
After a bit of research on google I found that setjmp on SPARC only saves the
stack pointer, the frame pointer and the program counter, which is why the
setjmp technique does not work. longjmp() on the other hand does do a window
flush in order to unroll stack frames.
--
Jason
On Thu, Nov 21, 2002 at 08:34:04AM +0100, Leopold Toetsch wrote:
My patch in 16237 has the code to flush register windows on v8 and older and v9
(64-bit) SPARC systems, which is what one is really trying to achieve via
setjmp.
--
Jason
unction raises an exception because you do not
know where or how the compiler has saved the registers.
--
Jason
ecode segments, as I do not expect one will JIT
compile every piece of code because of the inefficiency of doing that (unless
we make the JIT code less specialized than it is on at least IA-32/x86, where
addresses of registers and the interpreter pointer are embedded in the
generated code).
--
Jason
de generates an
exception ?
> * gets jumped to, so registers are still ok
> * saves processor registers to parrots
> * then longjmps to parrot handler
--
Jason
on is triggered in a C function
called from JIT code.
> * saves processor registers to parrots
> * then longjmps to parrot handler
>
> As we already seem to need to restore processor registers on resume, we
> could do the reverse thing on exception too.
>
>
> >Nicholas Clark
>
> leo
--
Jason
y, this will be necessary as the native code will need to transfer
control to an interpreter loop in order to execute code that has not been
compiled.
--
Jason
f gcc)
A lot of research has been done on this type of thing under the terms 'partial
evaluation' and 'specialization'. There is a working specializing python
compiler that might be of interest : http://psyco.sourceforge.net/doc.htm
--
Jason
on of the bytecode stored on disk. Having to
pseudo-execute the bytecode in order to disassemble seems unnecessary. I think
keeping this information separete from the executable section will make the
code generators simpler as well.
--
Jason
gned address on the stack (I can't imagine why). We could always say
"don't do that!" for performance reasons.
--
Jason
(I really don't see why).
Are you compiling with optimization enabled ? Is the difference consistent ?
If the answer to both questions is yes, it is probably a cache effect related
to the new variable on the function stack. I doubt the slowdown is universal.
I will try to check on SPARC sometime today.
--
Jason
lking function. This is left as an exercise for the reader.
--
Jason
Index: dod.c
===
RCS file: /cvs/public/parrot/dod.c,v
retrieving revision 1.24
diff -u -r1.24 dod.c
--- dod.c 23 Oct 2002 05:27:01 - 1.24
+++ dod.c
for (cur_var_ptr = lo_var_ptr;
(ptrdiff_t)(cur_var_ptr * PARROT_STACK_DIR) <
(ptrdiff_t)(hi_var_ptr * PARROT_STACK_DIR);
cur_var_ptr = (size_t)( (ptrdiff_t)cur_var_ptr +
PARROT_STACK_DIR * PARROT_PTR_ALIGNMENT )
--
Jason
is can be done by testing for preprocessor symbols
alone.
--
Jason
PDD ?
> perlhash/array have exists_keyed (but no type_keyed), though the opcodes
> are missing.
On a tangent:
Shouldn't a Perl Hash be a homogenous data structure, ie. it should contain
just PMCs ?
--
Jason
there is more than one DOD run ?
The problem sounds like that the collector is not looking in all the
appropriate places for these PMCs and Buffers. I have not looked in a while but
has anyone added the necessary code to examine CPU registers for PMC and Buffer
pointers ?
--
Jason
rrent state of the art is generational garbage collection, which
scans/copies longer lived data less frequently as it is more likely to remain
live.
--
Jason
as had the time and knowledge to do it.
--
Jason
1 - 100 of 275 matches
Mail list logo
