On Sun, Dec 15, 2013 at 11:28:02AM -0500, Parrot Raiser wrote:
: It's not really a constant he wants, but a value that's read-only to
: everything but the setting routine. Some sort of object, perhaps?
Any parameter to sub MAIN is readonly by default, since parameters
in general are readonly by de
On Sun, Dec 15, 2013 at 05:56:40PM +, Nicholas Clark wrote:
> With this, all NQP tests pass I can build the Rakudo setting, with a nursery
> size of 2048K.
>
> I have now written a script that will attempt to repeatedly recompile that
> far, each time dropping the nursery size by 1K, until so
On Sun, Dec 15, 2013 at 04:19:19PM +, Nicholas Clark wrote:
> (Again) I don't know what the correct fix is.
For now I'm working round it with this:
commit d3b4bca8139a5875e6a91d14896c2167ce36e23d
Author: Nicholas Clark
Date: Sun Dec 15 18:31:29 2013 +0100
XXX Unclear if this is corre
It's not really a constant he wants, but a value that's read-only to
everything but the setting routine. Some sort of object, perhaps?
On Sun, Dec 15, 2013 at 02:30:14PM +, Nicholas Clark wrote:
> I hacked up (somewhat literally) the attached 3 patches, to try to help
> automate GC debugging for MoarVM. The intent is to be able to change how
Next mole to whack:
$ gdb --args /home/nicholas/Sandpit/moar-g/bin/moar nqp.moarvm t
I hacked up (somewhat literally) the attached 3 patches, to try to help
automate GC debugging for MoarVM. The intent is to be able to change how
the nursery memory management is done, to swap in approaches more suitable
for debugging. Ideally I'd also like to be able to debug with
1) the nursery s
