>The question of building extensions has been kicked around on this list a >bit, but I still don't get it. >> >Is this hopeless? Is MacPerl not ready to have folks like me build extensions? I now have Code Warrior and am slowly learning how to use it. The main reason is that, under MPW, it is in fact impossible to write C code for use with Perl. (Someone please prove me wrong!) Just forget about CODE modules for Excel and Chipmunk Basic - they're simple. It's Perl itself that doesn't seem to desire such an easy interface with a defined calling sequence which is independent of internal Perl structures defined in obscure header files. "Advanced Perl Programming", Sriram Srinivasan, O'Reilly, helps but what you learn is that you have to recompile Perl itself to add a CODE module. (Once again will someone please prove me wrong!) There's a procedure in Code Warrior for creating modules which implement Mac traps and it's supposed to be simple. By Matthias. It's simple for him and probably for Chris but I haven't figured it out yet. It won't work under MPW. You can find samples in the distribution. -->From the USA, the only socialist country that refuses to admit it. ***** Want to unsubscribe from this list? ***** Send mail with body "unsubscribe" to mac-perl-request@iis.ee.ethz.ch