Leopold Toetsch <[EMAIL PROTECTED]> wrote:
Hi,
some changes not too long before the release did break pg.t. I was now
able to
track it down:
now the object constructor:
$I0 = find_type ['Pg';'Conn']
o_con = new $I0, con
does _not_ call
.sub init :vtable :method
anymore
it's calling init_pmc instead.
This change is just adding more mess to object construction and argument
passing.
I've made several attempts to unify object construction with new calling
convs
but no one seems to be listening :-(
That was a change I made (with Allison's approval). The purpose of the
change was to eliminate differences between PMCs and objects. It's confusing
for PMCs and objects and objects that subclass PMCs to behave differently.
Given that PMCs can have two different init functions, how does it make
sense for objects to have only one? Does providing an init function for a
subclass of a PMC override both of the parent's init functions?
--
Matt Diephouse
http://matt.diephouse.com
