class() calls constructor of previously created class about penlight

[stevedonovan]

Yeah, I see exactly what you mean - it's a sneaky feature. It allows a certain lazy style of inheritance; base ctor takes a string; subclasses can be made without explicit ctors, confident that the base ctor will be passed the string. Well, if you remember to pass it, of course - nasty stuff to document! I am tending towards 'everything is explicit' these days so maybe it should just go.

[asb]

But A:_init is an instance constructor - why would it ever be correct that it would be called when creating a new class? Have I not 1) created a new class and assigned it to A. 2) defined _init for class A and 3) created a new class and assigned it to B? Why should action 3) results in A:_init being called?

[stevedonovan]

Sorry, I misread you - I tried exactly the code you gave, and yes, I get also get a ridiculous result! Genuine, first class bug!

[stevedonovan]

This is very interesting - pl.class is one of the modules that changed - require 'pl.class' returns the actual class object. So if were

    class = require ('pl.class')

then things work fine - which is why I didn't see the problem at first. By some horrible fluke class.class exists and is a function, so everything looks hunky dory until it falls over.

[asb]

Ah I see, the previous version of Penlight I was using exported something like class, Map, and Set. But as you say it just returns pl.class now, so when I do require("pl.class").class the __index on the returned pl.class is called. This is a case of programmer error resulting from API breakage that probably turned out to cause more trouble than intended (due to the __index on pl.class). I'll mark it closed.

[stevedonovan]

What I will do is detect this particular case and issue a stern warning, otherwise it is going to cause confusion! (The other option is to regard it as an error)