SF Perl's Raku Study Group
We shall not cease from exploration, and the end of all our exploring will be to arrive where we started, The Raku Study Group: September 27, 1pm in California, 9pm in the UK Zoom meeting link: https://us02web.zoom.us/j/88535076025?pwd=MHBOTDltVitVMlh4R2Z5WUFaSDYwQT09 Passcode: 4RakuRoll https://www.meetup.com/San-Francisco-Perl/events/273537741/
Re: How to unbuffer $*IN
On 2020-09-26 David Santiago wrote: > I'm trying to capture key presses in the terminal and according to > raku's documentation i need to have $*IN unbuffered. You have to tell the terminal to stop buffering (AFAIK Raku doesn't buffer its inputs), which is not exactly trivial. You may be better off using https://modules.raku.org/dist/Term::ReadKey:cpan:JKRAMER (for example) -- Dakkar - GPG public key fingerprint = A071 E618 DD2C 5901 9574 6FE2 40EA 9883 7519 3F88 key id = 0x75193F88
How to unbuffer $*IN
Hi! I'm trying to capture key presses in the terminal and according to raku's documentation i need to have $*IN unbuffered. Can someone point me in the right direction on how to do that? Best regards, David Santiago
Re: New type Stash for Block is not a mixin type
Thank you, I'll see if I can concoct a self-contained example in order to open an issue. On Thu, Sep 24, 2020, 20:13 Elizabeth Mattijsen wrote: > Feels like a regression worthy of a Rakudo issue > > > On 24 Sep 2020, at 20:26, Fernando Santagata > wrote: > > > > Hello, > > > > Since I upgraded to the last Rakudo I'am having a weird problem. I have > a module like this: > > > > unit class Class1; > > etc. > > > > Then a second module: > > > > unit class Class2; > > use Class1; > > etc. > > > > In a program I need both modules, so it begins with two lines: > > > > use Class1; > > use Class2; > > etc. > > > > At this point if I run the program I get this error: > > > > New type Stash for Block is not a mixin type > > > > pointing to the line of code that uses Class2. If I remove the "use > Class1" line, that program works fine. > > But it bugs me, because I don't understand that behavior. > > > > Any hint? > > The whole thing worked fine using version 2020.07. > > > > -- > > Fernando Santagata >
