From doomvox at gmail.com Fri Jun 3 15:03:51 2022 From: doomvox at gmail.com (Joseph Brenner) Date: Fri, 3 Jun 2022 15:03:51 -0700 Subject: [sf-perl] The SF Perl Raku Study Group, 06/05 at 1pm PDT Message-ID: "Language is an artifact." Guru Lou Fonghoo Step 35 of the 85 steps of Fonghoosim (1972) The Raku Study Group June 6th, 2022 1pm in California, 9pm in the UK Zoom meeting link: https://us02web.zoom.us/j/83136957677?pwd=WXRSRkZ0SjZ4aGNJZ2l1OWM3OExqQT09 Passcode: 4RakuRoll RSVPs are useful, though not needed: https://www.meetup.com/san-francisco-perl/events/286342049 From doomvox at gmail.com Fri Jun 3 22:33:07 2022 From: doomvox at gmail.com (Joseph Brenner) Date: Fri, 3 Jun 2022 22:33:07 -0700 Subject: [sf-perl] The SF Perl Raku Study Group, 06/05 at 1pm PDT In-Reply-To: References: Message-ID: Let's try that again, without the typo on the date in the message body: it's on Sunday, June *5th*. "Language is an artifact." Guru Lou Fonghoo Step 35 of the 85 steps of Fonghoosim (1972) The Raku Study Group June 5th, 2022 1pm in California, 9pm in the UK Zoom meeting link: https://us02web.zoom.us/j/83136957677?pwd=WXRSRkZ0SjZ4aGNJZ2l1OWM3OExqQT09 Passcode: 4RakuRoll RSVPs are useful, though not needed: https://www.meetup.com/san-francisco-perl/events/286342049 From dpchrist at holgerdanske.com Sun Jun 5 19:05:24 2022 From: dpchrist at holgerdanske.com (David Christensen) Date: Sun, 5 Jun 2022 19:05:24 -0700 Subject: [sf-perl] Exporter and subroutine circular dependencies between modules In-Reply-To: <0878f511-92a1-9efb-dd96-137106005256@holgerdanske.com> References: <8e3ac525-d759-365c-8e26-3f395a784308@gmail.com> <1c0b502f-6acd-ef30-6648-aacbf1a4e7a5@gmail.com> <0878f511-92a1-9efb-dd96-137106005256@holgerdanske.com> Message-ID: <466f4dcb-3624-a4e3-daba-13f941cf52ec@holgerdanske.com> On 3/13/22 13:13, David Christensen wrote: > I have been wrestling with the Exporter module and subroutine circular > dependencies between modules for a number of years. https://www.mail-archive.com/module-authors at perl.org/msg10914.html We revisited this topic at a San Francisco Perl Mongers meeting today: https://mail.pm.org/pipermail/sanfrancisco-pm/2022-June/004851.html I showed the following snippet of code that demonstrates the solution I am currently using: 6 package Dpchrist::Lib5::Test; 7 8 9 use strict; 10 use warnings; 11 use threads; 12 use threads::shared; 13 14 our @EXPORT_OK; 15 16 BEGIN { 17 @EXPORT_OK = qw( 18 is_poly 19 ); 20 } 21 22 use parent qw( 23 Exporter 24 Test::Builder::Module 25 ); The key points are: * Put the Exporter-related statements (lines 14-25) near the top of the module, before other code. * Statement ordering is important: * First -- declare @EXPORT_OK, but do not define/ initialize it (line 14). * Next -- define/ initialize @EXPORT_OK in a BEGIN block (lines 16-20). * Finally -- 'use parent' to inherit from Exporter (lines 22, 23, and 25). * The above module also happens to inherit from Test::Builder::Module. My other modules do not need or have line 24. * As I develop code and introduce bugs, I frequently see warnings to the effect "subroutine redefined" when there is a circular loop between modules. Once I fix the bugs, those warnings go away. Without understanding the "how" and "why" of perl(1), Exporter, "compile time", "run time", "require", "use", "parent", "import", etc. -- of the several solutions myself and others have tried over time, this one seems to work the best for me. David From doomvox at gmail.com Fri Jun 17 10:06:42 2022 From: doomvox at gmail.com (Joseph Brenner) Date: Fri, 17 Jun 2022 10:06:42 -0700 Subject: [sf-perl] The SF Perl Raku Study Group, 06/19 at 1pm PDT Message-ID: Frederick P. Brooks, from the additional material in the 1995 edition of "The Mythical Man-Month" (1975): "Much more is known today about software engineering than was known in 1975. Which of the assertions in the original 1975 edition have been supported by data and experience? Which have been disproved? Which have been obsoleted by a changing world? ... " "Most of these propositions are operationally testable. my hope in putting them forth in stark form is to focus readers' thoughts, measurements, and comments." The Raku Study Group June 19th, 2022 1pm in California, 9pm in the UK Zoom meeting link: https://us02web.zoom.us/j/88131904373?pwd=UXh4eko4c1pHK2llQTlIcnN5dnJpQT09 Passcode: 4RakuRoll RSVPs are useful, though not needed: https://www.meetup.com/san-francisco-perl/events/286635701/ From wjm1 at caa.columbia.edu Tue Jun 21 12:31:03 2022 From: wjm1 at caa.columbia.edu (William Michels) Date: Tue, 21 Jun 2022 12:31:03 -0700 Subject: [sf-perl] The SF Perl Raku Study Group, 06/19 at 1pm PDT In-Reply-To: References: Message-ID: At the last Raku Study Group (Meetup), Joseph brought up an issue he's noticed with Raku's capture markers, `<(`...`)>`. Just noting here (for posterity) that the SO issue below might be an identical--or related--observation: https://stackoverflow.com/questions/63426361/raku-effect-of-capture-markers-is-lost-higher-up HTH, Bill. On Fri, Jun 17, 2022 at 10:06 AM Joseph Brenner wrote: > Frederick P. Brooks, from the additional material in the 1995 > edition of "The Mythical Man-Month" (1975): > > "Much more is known today about software engineering than > was known in 1975. Which of the assertions in the original > 1975 edition have been supported by data and experience? > Which have been disproved? Which have been obsoleted by a > changing world? ... " > > "Most of these propositions are operationally testable. > my hope in putting them forth in stark form is to focus > readers' thoughts, measurements, and comments." > > The Raku Study Group > > June 19th, 2022 1pm in California, 9pm in the UK > > Zoom meeting link: > > https://us02web.zoom.us/j/88131904373?pwd=UXh4eko4c1pHK2llQTlIcnN5dnJpQT09 > > Passcode: 4RakuRoll > > RSVPs are useful, though not needed: > https://www.meetup.com/san-francisco-perl/events/286635701/ > _______________________________________________ > SanFrancisco-pm mailing list > SanFrancisco-pm at pm.org > https://mail.pm.org/mailman/listinfo/sanfrancisco-pm > -------------- next part -------------- An HTML attachment was scrubbed... URL: