Etienne Kneuss

home » news » PHPT Generator used to discover documentation problems

SPL Datastructures

The Standard PHP Library was recently completed by a couple of data structures, namely heaps and doubly linked lists. You can find more information about those on
php.net/spl.datastructures

Feeds available

You can read colder.ch directly from the rss/atom feeds:
rss general RSS (general)
rss php RSS (PHP)
atom general Atom (general)
atom php Atom (PHP)

New design : Clearblue

I've made a new skin using the same design with blue colors: Clearblue. Check it out

New website

As you can see, the website has changed completely. I've re-designed everything using different types of technology to give an overall improvement. Take a look in the news section for detailed information.

PHPT Generator used to discover documentation problems The 6th of December 2006 @ 17:52

I commited a patch to docweb, some days back, to allow the generation of the complete package of phpt files. Those phpt files were generated from doc examples.

The main use of those phpt files was to have an easy way to check examples used in the documentation. Along with a php script analyzing the results and Hannes' great testing environment, I was able to generate a summary of the examples failing:

The results are quite interresting:

  1. 251 tests were generated
  2. 126 (50%) passed the checks
  3. 23 (9%) tests failed because of a missing extension
  4. 102 (41%) tests failed because of an error in the example (11% of them were caused by whitespace issues only)

There is thus potentially 80-90 examples in the documentation that contain errors!

Let the massive example bug squashing party begin !

Comments

11.12.2006 #1 giunta.gaetano

Not really an automated procedure, but lots of those pesky doc errors have one (or more) user entries that describe them at length af often give the correct version.
Maybe if editors where a bit more attentive to the user comments... (yes, I know they are a busy lot ;)

29.12.2006 #2 ludvig.ericson

Hah, yeah well I think all of them should have one or two errors, makes a great way of copy-paste protection :-)

Love your php.net kind-of-CAPTCHA :-)

28.01.2007 #3 philip

ludvig has a good idea, implement parse errors as a copy-paste counter-measure... I like it! :)

Add a comment

Username:

Spam Challenge: 2+13=?

Comment: