Re: PECL doc proposal

* Thus wrote Philip Olson: > > from configure.xml > --------------------------- > <para> > &pecl.linux.php45; > <ulink > url="&url.pecl.package;crack">&url.pecl.package;crack</ulink>. > In order to use these functions, you must compile PHP with Crack support > by using the <option role="configure">--with-crack[=DIR]</option> > option. > </para> > <para> > Windows users will enable <filename>php_crack.dll</filename> in order to > use these functions. > &pecl.windows.php45; > </para> > > from language-snippets.ent > --------------------------- > <!ENTITY pecl.windows.php45 'In PHP 4 this DLL resides in the > <filename>extensions/</filename> directory within your PHP > Windows binaries download. In PHP 5 it can be found in the > separate <ulink url="&url.pecl;">PECL</ulink> download from > <ulink url="&url.php.downloads;">PHP Downloads</ulink>.'> > > <!ENTITY pecl.linux.php45 'In PHP 4 this PECL extensions source > resides in the <filename>ext/</filename> directory within the PHP > sources. In PHP 5 this is no longer bundled and instead can be > found in <acronym>PECL</acronym> here:'> I think this is an excellent aproach to the current problem, I've been strugling with this myself. The only problem I see is the name of the ID of the entity. From my understanding is that a lot of stuff that resides currently in ext/ will be moved to PECL, so when version 5.1 comes out what will we do in that case? an entity of pecl.(windows|unix)4551 of of some sort would have to be made. And each release of php will have to create a new entity of some sort. Now after thinking about it, mabey if we can find a nice solution with the documentation's changelog (as you previously mentioned). These items could go there, and would be really nice if the function could reference that changelog somehow. Curt -- First, let me assure you that this is not one of those shady pyramid schemes you've been hearing about. No, sir. Our model is the trapezoid!