From: | Bruce Momjian <maillist(at)candle(dot)pha(dot)pa(dot)us> |
---|---|
To: | dg(at)illustra(dot)com (David Gould) |
Cc: | brett(at)work(dot)chicken(dot)org, hackers(at)postgreSQL(dot)org |
Subject: | Re: [HACKERS] perl/perl5 |
Date: | 1998-03-23 14:28:18 |
Message-ID: | 199803231428.JAA14003@candle.pha.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> If you ask a perl4 question on the comp.lang.perl, well, just lets say you
> won't be "helped" much. The offical perl position is the perl4 is an
> obsolete nightmare that they are all trying to forget as rapidly as possible
> and that perl5 is the bright shiny present and future. That is, perl4
> is not supported anymore, please upgrade etc...
>
> So, given that it is pretty darn easy to get perl5 these days, it has been
> out for a few years with good results, is very compatible with perl4 anyhow,
> and really is better for a number of reasons, I see no reason to continue
> to support perl4.
>
> Lets just do it. If for some obsolete platforms like SCO or suchlike this
> means that they will have to download perl5 and pgsql, so be it. The DB
> support is so much better it will be doing them a favor anyway...
OK, I will leave our code alone. Our Makefile.PL requires perl5, and
BSD/OS has perl as pel5, so if other people had problems doing make of
interfaces/perl5, I was going to add code to look for perl5 first, and
use perl only if a perl5 binary did not exist, but if no one else has
this problem, it is not worth changing it.
--
Bruce Momjian | 830 Blythe Avenue
maillist(at)candle(dot)pha(dot)pa(dot)us | Drexel Hill, Pennsylvania 19026
+ If your life is a hard drive, | (610) 353-9879(w)
+ Christ can be your backup. | (610) 853-3000(h)
From | Date | Subject | |
---|---|---|---|
Next Message | Meskes, Michael | 1998-03-23 14:59:41 | RE: [HACKERS] problem with current snapshot |
Previous Message | Michael Meskes | 1998-03-23 14:09:23 | just another standards question |