Am 17.04.2015 um 04:34 schrieb Nathan Gray:
# Call it if it is a routine. This will capture if requested.
return (var)(self) if nqp::istype(var,Callable);
This seems to indicate that captures in the embedded regexes
should capture.
On Fri, Apr 17, 2015 at 09:47:22AM +0200, Tobias
On Wed, Apr 15, 2015 at 09:45:39PM -0400, Nathan Gray wrote:
I had given up on using regexes embedded within regexes, because
I could not get capturing to work.
I did a backtrace on one of the test cases that fails, which led
me to
src/core/Cursor.pm
in
method INTERPOLATE(\var, $i = 0
I've been playing in Perl 6 (after several years of absence). I
am very impressed.
I'm porting my recent Date::Reformat into Perl 6, for fun,
to get me back into the Perl 6 headspace, and possibly to help
others, either with something useful, or something they can look
to for examples.
I've run
I am working on a small virtual organ program, where I have
multiple MIDI controller keyboards which can be connected to one
or more synthesizer channels to emit various sounds
simultaneously.
At this point, I am able to read events from a single MIDI
controller and send the events to the correct
On Fri, Jan 01, 2021 at 03:20:09PM -0500, Vadim Belman wrote:
> As it seems that Audio::PortMIDI lacks non-blocking interface, I think a
> solution would be to read events in a dedicated thread and re-submit them
> into a Supplier. Something like:
>
> my Supplier $midi-events;
>
> start {
>
I have a program that I intend to run for days or weeks at a
time, but it is being killed by the OS after a day or so, I think
because it is using up too much memory (growing over time). I
would like to be able to debug the memory leak and find out where
it is happening, so I can fix it.
What