i'm very happy this topic's turned up and i've taken notice of it. i'm
operating 3 websites with more less dynamic content like database
interaction. php was my way of learning how to program or rather do the
scripting. it's obvious that perl is much more powerful, but since build
622 i know what php3 can mean... i tried to create a socket with perl (one
server/one client side script). the 622 build implements the urgently
required fork() (without this function the perlipc example i've taken
(hardly understood btw) for the client side wouldn't work) functionality
for multithreading in a perl script.. but pitty.. there is no dbi module
for this latest verion of activestates perl... however... trying to create
a socket under perl seperates those 'scripters-on-demand'* like i am one
from those c/c++/perl veterans... i didn't understand a line of the
suggested script... trying this with php3 cost me 10 minutes and it worked
(i didn't really need the multithreading stuff).
finally think of the dbi module. when i started to operate on mysql
databases via perl i've read the docs fo this module. that realy did it. i
never came to the idea of looking into the dbd:mysql manual for valid
instructions. no word in the dbi manual that most of the functions don't
apply to mysql databases - or that the instruction set doesn't apply to all
databases supported by the dbi manual. how am i ordinary wannabe programmer
supposed to get behind this.
i'm sure there are a lot out there with not the slightest idea why their
perl script don't work because the documentation only serves the already
knowing. php3 is much more efficient there, no mdoules, allalready onboard
(think of the default url en/decoding while passing form elements). but,
never mind that. i just want to say that people like me need and will need
in future php AND perl - and i'm sure there are more out there.
greetings
oliver schleede
---
You are currently subscribed to perl-win32-users as: [[email protected]]
To unsubscribe, forward this message to
[EMAIL PROTECTED]
For non-automated Mailing List support, send email to
[EMAIL PROTECTED]
