skeleton module?

In the beginning, I just thought about rewriting magick (ImageMagick) module from PHP3. But after starting to write it from scratch, a thought came... there's a lot of necessary things to write when starting a new module, the minimal code needed seems to be always the same, so why in the hell not write a script to do it? So, I took ext_skel as a starting point, wrote some skeleton code (not exactly finished or perfect yet), and now I've got a script called create_module. When you call it like 'create_module foobar', it creates directory ext/foobar and files Makefile.in, config.m4, foobar.c, php_foobar.h and foobar.php in it. After just tweaking config.m4 and doing ./buildconf; ./configure --[with|enable]-foobar, it's ready to be compiled in PHP4 and contains even one example function, foobar_test() (that's why there's that foobar.php file, to check that the tests in config.m4 went through and the module was compiled in). Thoughts? To myself, seems a really good idea (wouldn't have bothered otherwise). Should I just add and commit it, so you can see what I'm trying to do. -- Jouni