Personally, after all the work I have done over the past 2=
5 years to make mod_perl what it is today, I could care less about making i=
t easy for other people to avoid patching source code to perl itself.v>


--00000000000006691c06115d176e--

--===============1846383458==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Hangout mailing list
Hangout-at-nylxs.com
http://lists.mrbrklyn.com/mailman/listinfo/hangout

--===============1846383458==--

--===============1846383458==
Content-Type: multipart/alternative; boundary="00000000000006691c06115d176e"

--00000000000006691c06115d176e
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Personally, after all the work I have done over the past 25 years to make
mod_perl what it is today, I could care less about making it easy for other
people to avoid patching source code to perl itself.

If you don't like the performance gains of using :Sealed subroutines on
your mod_perl handlers, you can always not use it.

On Wed, Feb 14, 2024 at 2:42=E2=80=AFPM Ed Sabol w=
rote:

> On Feb 14, 2024, at 2:27 PM, Joe Schaefer wrote:
> > sealed.pm is really only necessary in a mod_perl context. And really it
> only matters if you are using subrequests to reenter :Sealed handlers.
> Otherwise I don't see the point of the exercise.
>
> Well, I suppose one point of the exercise would that a person who wants t=
o
> do this wouldn't have patch and compile Perl, but if you don't think
> there's any value in that, then OK.
>
> Regards,
> Ed
>
>

--00000000000006691c06115d176e
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Personally, after all the work I have done over the past 2=
5 years to make mod_perl what it is today, I could care less about making i=
t easy for other people to avoid patching source code to perl itself.

<=
br>

If you don't like the performance gains of using :Sealed =
subroutines on your mod_perl handlers, you can always not use it.

v>

On W=
ed, Feb 14, 2024 at 2:42=E2=80=AFPM Ed Sabol <abol-at-gmail.com">edwardjsabol-at-gmail.com> wrote:

class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px sol=
id rgb(204,204,204);padding-left:1ex">On Feb 14, 2024, at 2:27 PM, Joe Scha=
efer <joe-at-sunsta=
rsys.com> wrote:

> seal=
ed.pm is really only necessary in a mod_perl context. And really it onl=
y matters if you are using subrequests to reenter :Sealed handlers.=C2=A0 O=
therwise I don't see the point of the exercise.



Well, I suppose one point of the exercise would that a person who wants to =
do this wouldn't have patch and compile Perl, but if you don't thin=
k there's any value in that, then OK.



Regards,

Ed

--00000000000006691c06115d176e--

--===============1846383458==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Hangout mailing list
Hangout-at-nylxs.com
http://lists.mrbrklyn.com/mailman/listinfo/hangout

--===============1846383458==--