I can't read the notation as for example I can with the PHP mysql
functions.
Interestingly, when I Googled this subject, I encountered a note saying
that the latest PHP API for MySQL is OO not procedural. I didn't read it
carefully, but I got the impression that if you upgrade MySQL you'd have
to switch to the OO API.
I'm afraid the world is moving from procedural to OO. I may be wrong but
I suspect module writers nowadays prefer to write OO APIs.
Sure, I can copy an example with minus greater-than notation from a
tutorial ---
I recommend you try to think of a->b as an *arrow* notation. The object
has a pointer to a subroutine, you use that pointer to call the
subroutine (sloppy terminology for simplicity).
but in an hour, tomorrow, a week later, it's all greek
to me.
I recommend you write yourself a few simple Perl OO toy programs. I
found it a good way to get familiar with Perl OO paradigms. There are
some good tutorials around and it only needs an hour or so if you have
any prior exposure to OO concepts.
perldoc perlboot; #
http://perldoc.perl.org/perlboot.html
perldoc perltoot; #
http://perldoc.perl.org/perltoot.html
It isn't remotely perlish,
It isn't Perl4ish but it is Perl5ish IMHO.
which would be something like:
opendb(MYDBHANDLE," gory details of db connection here");
and so forth.
Maybe you could write a procedural wrapper for the OO API. Fill the
wrapper with copious comments to yourself. You could centralise this
into a procedural module. I've no idea how feasible this is for you (or
anyone indeed), but it's an idea†you could consider.
Sorry not to be of more help.