Meeting tomorrow

Darren Duncan darren at DarrenDuncan.net
Tue Oct 15 16:11:40 CDT 2002


On Tue, 15 Oct 2002, Peter Scott wrote:
> Victoria.pm will meet tomorrow, Wednesday October 16, at UVic's
> McPherson Library.
> Meet inside in the art gallery area immediately to the right upon
> entering between 6:45 and 7:00.
<snip>

Despite what I said the other week, I should still be able to attend for
the whole thing.  I will just leave downtown on a 10pm bus rather than the
8:35pm, which should give me time to be at the whole talk and travel from
UVIC afterwards.  So lookin' good.

> At 7:00 we will relocate to one of the small conference rooms on the
> next floor up.  We will leave a note with the room number in the art
> gallery area; if you don't find it, ask the librarian where the
> conference rooms are and look through their doors which sport handy
> windows for this purpose until you find some people having way too much fun.
>
> Topic TBD, but this may be the night we finally have the
> Object-Oriented Perl talk!

Of course, if the last meeting was any indication, we either can only have
it if one of the attendees doesn't already have experience with objects,
or if we all do and we want to take it to an advanced level.

In any event, to give you an idea where I am coming from, I can't think of
any specific problems I am having that I need help with, but I welcome the
chance to learn other new things through discussion, or to help other
people.

On the other hand, I am wanting to make a new generic module or set of
modules and did want some feedback of whether other people could use this
kind of functionality, making it a CPAN candidate.  That is, the problem I
am trying to solve with these modules, transparent portability over
multiple database vendors, has already been addressed by several other
distributions on CPAN, but my proposed solution would be significantly
different from the others.  Or is it unique enough?  That is what I would
want to ask.  Note that I would not be addressing the binary API
portability issue that DBI does well, but rather SQL/feature portability,
which is higher-level.  Details would come verbally, unless it would be a
good idea to share a written version first?

Have a good day. -- Darren Duncan





More information about the Victoria-pm mailing list