I would like to work on perl6-debug. But where to start? I am daunted by the prospect.
Some questions - hopefully easy to answer. 1) In earlier updates there was a perl6-debug executable. Was this just a link to perl6-debug-m? 2) perl6-debug worked before, and then stopped working. You said 'bit-rotted'. I would think that it would help to discover at what point the debug version stopped working and then to look at the commits to see what changed. That would narrow down what needs modifying. Do you think this is a good strategy? More difficult questions, but you may know answer. 3) Why is it not possible to arrange for a break inside a module? I realise it is because modules are 'pre-compiled', but is there a way either (1) to prevent pre-compilation (that is for the module to be included so that it is compiled with the main programe, or (2) to arrange for a module to be compiled with debug information (sort of like -dev modules in Debian). Finally, I was thinking about making a GUI or perhaps linking it to Atom. Your comments would be helpful. Richard On Tuesday, June 06, 2017 06:43 AM, Zoffix Znet via RT wrote: > On Mon, 05 Jun 2017 14:45:26 -0700, rnhainswo...@gmail.com wrote: >> If rakudobrew is only for core hackers, then why is it on the rakudo >> site as the best way to get rakudo? > Is that on rakudo.org? I see some mention of rakudobrew on > http://rakudo.org/how-to-get-rakudo/ > pending updates to the page[^1], but the very first sentence of even that > page reads "The recommended way to use Rakudo is by downloading Rakudo Star" > > [1] https://rt.perl.org/Ticket/Display.html?id=130500#ticket-history > >> I now know that perl6-debug-m is bit rotted, but I quote from 5 >> December >> 2012 (https://perl6advent.wordpress.com/2012/12/05/a-perl-6- >> debugger/): > You should probably double check the dates on posts that show up in Google. > This one for example was written 5 years ago, which is 3 years before the > first stable language version was even released. Lots of things changed. > >> It seems to me that rather than trying to remove all mention of the >> debugger, would be to place a notice on perl6.org or on rakudo.org, >> and > I think you misunderstood. I was talking about removing rakudobrew, > not the debugger. Rakudobrew has many quirks and people never bother > to read its documentation to learn about them. Not to mention it builds > a HEAD commit by default, leaving the user open to (potentially serious) bugs. > >> It is a shame that this has happened because it seems a step >> backwards. > This project is largely driven by volunteers. You're welcome to join the > effort to keep broken things unbroken :)
