From kominetz at gmail.com  Mon Feb 11 12:46:16 2019
From: kominetz at gmail.com (John Kominetz)
Date: Mon, 11 Feb 2019 15:46:16 -0500
Subject: [Philadelphia-pm] Monday, Jan 14
In-Reply-To: <51255125-c5d8-4858-a189-09ab1d768d65@www.fastmail.com>
References: <20190111150049.GA21117@localhost> <20190125214048.GC15939@debian>
 <d48d639f-aef2-c029-54cf-5b3ec2ab28ca@phoenyx.net>
 <20190126133621.GA6833@localhost>
 <1548814922.765832123@apps.rackspace.com> <20190130124051.GB9862@mawode.com>
 <51255125-c5d8-4858-a189-09ab1d768d65@www.fastmail.com>
Message-ID: <CADTpxcNoxV5gLoX1+dFhZ5WmgoFxqsfcu3UhTOO5yJ5COiDDbA@mail.gmail.com>

Sorry to be late to the conversation, but Monday is generally better for me
since i?m usually WFH, and I have another event this Wed. Anyway, have fun
bisecting!

On Wed, Jan 30, 2019 at 09:32 Brian Duggan <bduggan at matatu.org> wrote:

> Okay --- so we are on for the 13th -- the second Wednesday
> of the month -- let's pencil that in as a recurring event
> and see if it works :D
>
> Brian
>
> On Wed, Jan 30, 2019, at 7:41 AM, Walt Mankowski wrote:
>
> Oh right, the first Wednesday would be tough for me, too because of
> that.
>
> Walt
>
> On Tue, Jan 29, 2019 at 09:22:02PM -0500, rgeoffrey at platypiventures.com
> wrote:
> >
> > The first Wednesday is PLUG Central [ http://www.phillylinux.org/ ](
> http://www.phillylinux.org/ ).
> >
> >
> > -----Original Message-----
> > From: "Brian Duggan" <bduggan at matatu.org>
> > Sent: Saturday, January 26, 2019 8:36am
> > To: philadelphia-pm at pm.org
> > Subject: Re: [Philadelphia-pm] Monday, Jan 14
> >
> >
> >
> > Hi Folks,
> >
> > Meeting on Wednesdays sounds good -- I should be able to get
> > a room. Tue/Thu are unfortunately out for me. Maybe a bit
> > earlier in the evening? Shall we try for 6pm on the first
> > Wednesday of the month?
> >
> > I think we originally chose Mondays to avoid conflicts
> > with a few other meetups -- but I can't remember which
> > ones :-)
> >
> > Also, Jim has already kindly offered to come down from NYC
> > to give a talk on Monday February 11th -- so we may have to
> > wait until March for the switcheroo.
> >
> > Brian
> > _______________________________________________
> > Philadelphia-pm mailing list
> > Philadelphia-pm at pm.org
> > https://mail.pm.org/mailman/listinfo/philadelphia-pm
>
> > _______________________________________________
> > Philadelphia-pm mailing list
> > Philadelphia-pm at pm.org
> > https://mail.pm.org/mailman/listinfo/philadelphia-pm
>
>
> _______________________________________________
> Philadelphia-pm mailing list
> Philadelphia-pm at pm.org
> https://mail.pm.org/mailman/listinfo/philadelphia-pm
>
>
> *Attachments:*
>
>    - signature.asc
>
>
> _______________________________________________
> Philadelphia-pm mailing list
> Philadelphia-pm at pm.org
> https://mail.pm.org/mailman/listinfo/philadelphia-pm
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mail.pm.org/pipermail/philadelphia-pm/attachments/20190211/213f8302/attachment.html>

From jkeenan at pobox.com  Wed Feb 13 22:05:26 2019
From: jkeenan at pobox.com (James E Keenan)
Date: Thu, 14 Feb 2019 01:05:26 -0500
Subject: [Philadelphia-pm] Fwd: [perl #133737] Build-time failures with
 PERL_GLOBAL_STRUCT and PERL_GLOBAL_STRUCT_PRIVATE
In-Reply-To: <rt-4.0.24-30176-1550084658-1574.133737-94-0@perl.org>
References: <rt-4.0.24-30176-1550084658-1574.133737-94-0@perl.org>
Message-ID: <7bc1de8a-ed7a-c6d0-b7dd-c48c5e84966e@pobox.com>

Coincidentally, today there was some discussion on p5p about two of the 
weird configuration options for Perl 5!


-------- Forwarded Message --------
Subject: [perl #133737] Build-time failures with PERL_GLOBAL_STRUCT and 
PERL_GLOBAL_STRUCT_PRIVATE
Date: Wed, 13 Feb 2019 11:04:18 -0800
From: Jarkko Hietaniemi via RT <perlbug-followup at perl.org>
Reply-To: perlbug-followup at perl.org
To: jkeenan at pobox.com

[Karl found me gathering dust in a closet]

So yes, the global struct config was created for Symbian, which is dead 
as a dodo.  The probability of still existing Symbian phones getting 
Perl installed is extremely low.

But more generally, the config was not Symbian-specific as such.
It was  created to cover for a limitation in Symbian, and that was
"shared  libraries shall not have writeable data" (they could have
data, but only read-only).  In more modern operating systems the
writeable data sections of shared libraries are copy-on-write

The global struct is a bit misleading as terms go: what it does is that 
it pulls all the global data into a single struct, which can then be 
heap-allocated in main, and just passed around.  So it is "a struct for 
globals", not a "global" "struct".  The feature comes in two flavors,
vanilla and PRIVATE,the latter of which is really strict: it leaves
not even the global struct visible, but instead a function call
through which you can access the the struct.  (The description
I wrote (I think) for perlguts is still good.)

I still find the config useful as a cleanliness exercise: do we have a 
good enough understanding and tracking of the global data so that we
can move all of it to heap, making the shared library as "pure" as possible.
But then  again, as the creator of the feature I am biased.

From bduggan at matatu.org  Thu Feb 14 06:09:16 2019
From: bduggan at matatu.org (Brian Duggan)
Date: Thu, 14 Feb 2019 09:09:16 -0500
Subject: [Philadelphia-pm] Fwd: [perl #133737] Build-time failures with
 PERL_GLOBAL_STRUCT and PERL_GLOBAL_STRUCT_PRIVATE
In-Reply-To: <7bc1de8a-ed7a-c6d0-b7dd-c48c5e84966e@pobox.com>
References: <rt-4.0.24-30176-1550084658-1574.133737-94-0@perl.org>
 <7bc1de8a-ed7a-c6d0-b7dd-c48c5e84966e@pobox.com>
Message-ID: <20190214140916.GA30922@localhost>

Nice!

Thanks for the talk, Jim.

Folks -- next month the second Wednesday doesn't
work for me so I set the date to March 20th --
we can revisit this as it gets closer.

Happy ??-day everyone
Brian

On Thursday, February 14, James E Keenan wrote: 
> Coincidentally, today there was some discussion on p5p about two of the
> weird configuration options for Perl 5!
> 
> 
> -------- Forwarded Message --------
> Subject: [perl #133737] Build-time failures with PERL_GLOBAL_STRUCT and
> PERL_GLOBAL_STRUCT_PRIVATE
> Date: Wed, 13 Feb 2019 11:04:18 -0800
> From: Jarkko Hietaniemi via RT <perlbug-followup at perl.org>
> Reply-To: perlbug-followup at perl.org
> To: jkeenan at pobox.com
> 
> [Karl found me gathering dust in a closet]
> 
> So yes, the global struct config was created for Symbian, which is dead as a
> dodo.  The probability of still existing Symbian phones getting Perl
> installed is extremely low.
> 
> But more generally, the config was not Symbian-specific as such.
> It was  created to cover for a limitation in Symbian, and that was
> "shared  libraries shall not have writeable data" (they could have
> data, but only read-only).  In more modern operating systems the
> writeable data sections of shared libraries are copy-on-write
> 
> The global struct is a bit misleading as terms go: what it does is that it
> pulls all the global data into a single struct, which can then be
> heap-allocated in main, and just passed around.  So it is "a struct for
> globals", not a "global" "struct".  The feature comes in two flavors,
> vanilla and PRIVATE,the latter of which is really strict: it leaves
> not even the global struct visible, but instead a function call
> through which you can access the the struct.  (The description
> I wrote (I think) for perlguts is still good.)
> 
> I still find the config useful as a cleanliness exercise: do we have a good
> enough understanding and tracking of the global data so that we
> can move all of it to heap, making the shared library as "pure" as possible.
> But then  again, as the creator of the feature I am biased.
> _______________________________________________
> Philadelphia-pm mailing list
> Philadelphia-pm at pm.org
> https://mail.pm.org/mailman/listinfo/philadelphia-pm