Hi! > It really depends what you'd like to do. You reported you're fluent in C++. > Something quite interesting would be to enable push-parser in lalr1.cc. It's > more ambitious than the subcomplain task, but it will probably take you less > time, because it's more compact, it will impact much less code.
Ok, seems very interesting! I use C++ (currently C++17) in my daily job as a developer and I always try to keep up with the latest of the standard. I will familiarize myself first with push/pull parsers and then I will start with it 😊 I will also take a look at TODO to check if there is already any specification about how it should look like. Regards, Victor -----Original Message----- From: Akim Demaille <[email protected]> Sent: 2020年2月19日 21:39 To: Morales Cayuela, Victor (NSB - CN/Hangzhou) <[email protected]> Cc: Bison Bugs <[email protected]>; Bison Patches <[email protected]> Subject: Re: Getting involved in Bison Hi Victor, > Le 18 févr. 2020 à 08:19, Morales Cayuela, Victor (NSB - CN/Hangzhou) > <[email protected]> a écrit : > > Hello Akim, > > It did not ruin my will to continue contributing! Great news! > It took me more time than expected to finish it because I did not know how to > retest cases fast and it became quite tiresome (at the beginning I even > copied the failing input.y code to a temporary file and then ran bison > manually XD). There's 'make recheck' to rerun the failures, or `make check-local TESTSUITEFLAGS='1 2 3'` just to run tests 1 2 and 3. See README-hacking. > I must also thank you for helping me fixing the remaining bugs in the code > and in the testcases. Definitely my job! Happy to help! > What could I do next? :) Gee... Lemme think... It really depends what you'd like to do. You reported you're fluent in C++. Something quite interesting would be to enable push-parser in lalr1.cc. It's more ambitious than the subcomplain task, but it will probably take you less time, because it's more compact, it will impact much less code. WDYT?
