_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204=
,204);padding-left:1ex">Many thanks.

Nowadays, we tend to deal increasingly with Linux servers rather than Win32=
/64, but it is

nice anyway that someone cares for this, as we still have some customers wi=
th legacy Win

servers that they want to keep and update from time to time.

(And it is also nice for our development/support workstations).



We have quite a few real-world applications based on perl and mod_perl, whi=
ch in

themselves have been running reliably for years without any needed changes =
due to perl itself.

But we do get in trouble from time to time because customers insist on chan=
ging the

platform on which these applications are running.



By the way, and in the somewhat OT gist of the discussions about perl's=
evolution, I feel

that there is one argument about perl that is being consistently overlooked=
and/or

undervalued :

The fact that applications written in perl many years ago (as much as 20 ye=
ars sometimes),

are still running unchanged today, despite numerous changes of versions, pl=
atforms, OS'es

etc.. (*)

I do not think that there is *any* other current programming language (or &=
quot;framework")

which equals that record.



This may sound a bit like a "dinosaur" argument, but just think o=
f all the=C2=A0 time and

resources (and thus ultimately, money) which people programming in other la=
nguages have

had to spend during the same period, just to keep the same things running, =
and you can get

a measure of perl's "productivity" in comparison.



I totally understand the desire of some to modernise perl and make it more =
attractive to

new generations of programmers. But it would be a shame if in the process, =
perl (5,7) lost

this rather unique quality and positioning.



P.S. And of course, that longevity and stability of perl, is all to the cre=
dit of people

like you, who have been supporting and maintaining it over the years, for (=
in my view)

much too little public recognition and reward in the end.



(*) a bit more on topic : the most "traumatic" events in those ma=
ny years as far as our

perl programming was concerned, have been the changes from Apache 1.x to 2.=
0, and later

the changes from 2.2 to 2.4 in terms of AAA. (So, not in perl itself, but i=
n the way it

interacts with Apache).

I think that nothing else really "registered", even over many OSe=
s such as all the

versions of Windows-es, SunOS, Solaris, HP/UX, AIX, Unix-es, Linux, to name=
only the few

which I remember running our applications on. Applications of which we only=
ever needed

one version, running everywhere.



On 05.03.2021 13:12, Steve Hay wrote:

> For those who are interested, I have uploaded a 64-bit build of

> mod_perl-2.0.11 and libapreq2-2.15 components compatible with Apacher>
> Lounge 2.4.46 (Win64, VC16, built 18 February 2021) and Strawberry

> Perl 5.32.1.1 (64bit).

>

> You can download it from: ay/" rel=3D"noreferrer" target=3D"_blank">https://people.apache.org/~steveh=
ay/

>

> The SHA1 digest is: 33e231eb91901007e25fd78eb5643901672c519b

>

> Regards,

> Steve

>