Re: ext/pspell/config.m4

From: Date: Wed, 03 Apr 2002 09:38:40 +0000
Subject: Re: ext/pspell/config.m4
References: 1  Groups: php.dev 
Request: Send a blank email to php-dev+get-82046@lists.php.net to get a copy of this message
At 18:21 4/2/2002 -0800, Vlad Krupin wrote:
The problem is that now we have yet another aspell, and on aspell website it says that it's the latest and the greatest, and our website (www.php.net/pspell and www.php.net/aspell) tells people to use pspell extension because aspell is old and deprecated (which is true with regard to the version of aspell that our aspell extensions supports). So, we have old aspell, which (hopefully) nobody uses. We have pspell, which people use. And we have new aspell, which has essentially the same API as pspell, but the name of the project has changed back to what it used to be 2-3 years ago. That becomes confusing, so I wanted to ask a question - what to do? Should we nuke aspell extension altogether because it's very old and update the documentation to tell people that pspell extension works with new aspell?
Yes, I think it's the best to do. There's a dummy pspell library created with the new aspell. It doesn't work for me though - should be a libtool problem - that explains the triple link tests in config.m4.
Should we make aspell extension work with both old and new aspell's (that's gonna be a lot of #ifdef's)? Should we just update the documentation to tell people that old aspell is not the same as new aspell, so, confusing as it is, they should not use aspell extension, but pspell extension instead?
Rename --with-spell and use --enable-spell-newaspell and --enable-spell-pspell? Sort of like the xslt extenstion. Should make the config.m4 file a lot easier to maintain also. For BC then map: --with-pspell to --with-spell --enable-spell-pspell and issue a warning.
I'm just curious if I can get any useful feedback on what it would make sense to do. Thanks, Vlad Melvyn Sopacua wrote:
Hi, I modified the above mentioned file, to allow the configuration with "The new Aspell" current cvs. Symbol HAVE_NEW_ASPELL is being defined, but currently unused. Initial tests on my system shows main functions working. More to come (testsuite). Please check if it works for other systems and apply if you find it to be correct. Met vriendelijke groeten / With kind regards, IDG.nl Melvyn Sopacua Webmaster ------------------------------------------------------------------------ --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.343 / Virus Database: 190 - Release Date: 22-3-2002
Met vriendelijke groeten / With kind regards, Webmaster IDG.nl Melvyn Sopacua

« previous php.dev (#82046) next »