My worry is that this change appears to have absolutely no positive
aspects and only negative potential. We know browsers exist that cannot
handle 4-digit years. Early WebTV boxes don't, early Netscape don't. We
do not know of any browsers that cannot handle 2-digit years. Hence I
fail
If Set 1 was truly empty, I'd agree with you.
-Rasmus
On Thu, 26 Sep 2002, Sascha Schumann wrote:
My worry is that this change appears to have absolutely no positive
aspects and only negative potential. We know browsers exist that cannot
handle 4-digit years. Early WebTV boxes don't,
On Thu, 26 Sep 2002, Rasmus Lerdorf wrote:
If Set 1 was truly empty, I'd agree with you.
So, amazon.com and bn.com alike are missing out business
opportunities? We should tell them! :)
Thus far, you only said that such software existed. Are you
now saying that you are
: [PHP-CVS] cvs: php4 / php.ini-recommended
On Thu, 26 Sep 2002, Rasmus Lerdorf wrote:
If Set 1 was truly empty, I'd agree with you.
So, amazon.com and bn.com alike are missing out business
opportunities? We should tell them! :)
Thus far, you only said that such software existed
On Thu, 26 Sep 2002, Sascha Schumann wrote:
On Thu, 26 Sep 2002, Rasmus Lerdorf wrote:
If Set 1 was truly empty, I'd agree with you.
So, amazon.com and bn.com alike are missing out business
opportunities? We should tell them! :)
Likely not, but given that set 2 is currently
On Thu, Sep 26, 2002 at 06:42:42AM -0700, Rasmus Lerdorf wrote:
Your reasoning is that somebody will at some point write a browser that
can't handle 2-digit years and thus we should risk breaking existing apps
for a small percentage of users. I think we should worry about this when
such a
I saw Sascha's commit for php.ini-dist. Nobody objects it so I merged it
to php.ini-recommended as it supposed to.
I'm 0 for both On and Off.
--
Yasuo Ohgaki
Rasmus Lerdorf wrote:
; Enforce year 2000 compliance (will cause problems with non-compliant browsers)
-y2k_compliance = Off
