Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:32782
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain seanius.net from 66.93.22.232 cause and error)
To: internals@lists.php.net
Date: Mon, 15 Oct 2007 19:10:45 +0200
User-Agent: KMail/1.9.7
Cc: Stefan Esser <stefan.esser@sektioneins.de>,
 Wez Furlong <wez@omniti.com>
References: <64ED731E-CA44-498E-9AF9-C9B00037B863@omniti.com> <47131626.5020809@sektioneins.de>
In-Reply-To: <47131626.5020809@sektioneins.de>
MIME-Version: 1.0
Content-Type: multipart/signed;
  boundary="nextPart1950269.vQ1f5IvAv4";
  protocol="application/pgp-signature";
  micalg=pgp-sha1
Content-Transfer-Encoding: 7bit
Message-ID: <200710151910.49707.seanius@seanius.net>
Subject: Re: [PHP-DEV] Large file support for PHP
From: seanius@seanius.net (sean finney)

--nextPart1950269.vQ1f5IvAv4
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

hi,

On Monday 15 October 2007 09:26:30 am Stefan Esser wrote:
> please keep in mind that compiling PHP with large file support breaks
> binary compatibility...
> One of the globals contain a "stat" struct that has different size for
> LFS or no LFS.

yes, this is of course a big deal for some people, esp if you're using=20
proprietary software that's built against the "original" abi.  of course if=
=20
you're only using OSS extensions, you can simply recompile them against the=
=20
new api/abi and there's no drawback.

btw - in our (debian's) case, the benefits outweighed the consequences, so=
=20
we've been shipping with LFS turned on for somewhere around a year now.


	sean

--nextPart1950269.vQ1f5IvAv4
Content-Type: application/pgp-signature; name=signature.asc 
Content-Description: This is a digitally signed message part.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQBHE58ZynjLPm522B0RAojfAJwIYkIFGFCKtY5R2zvHAdVUFzb6+gCfWMJt
G9S4p91vfzjWSnhL1NBeVak=
=LxiD
-----END PGP SIGNATURE-----

--nextPart1950269.vQ1f5IvAv4--