Is there a strict one-file-to-one-class convention now?
Reason I ask is, I have a problem with a file (entry.rb) that defines a base class (Entry) and about 10 subclasses (ContactInfo and a bunch more).
It loads fine the first time, but when the file gets unloaded and then reloaded, I get:
entry.rb:164: superclass mismatch for class ContactInfo
Line 164 is where ContactInfo is defined, which is the first class other than Entry defined in this file. I’m guessing the error happens because Entry is now a reference to a new class, while ContactInfo still points to the old “Entry” is its parent.
Looking at the code, it does seem like it have a one-file-one-class(-with-the-same-name-as-the-file) convention built-in.