> On 31 Aug 2015, at 04:51, Mark Bratcher <mdbra...@gmail.com> wrote: > > Holger
Hi! > I believe I found the problem. oops! > The socket is connecting fine. But digging into the connection code, I found > that a `class new` operation now automatically calls the `initialize` method > in 3.2.91-b98173d, but it does not do so in 3.2.5. This causes a problem in > the MySQLPacket and MySQLInputPacket connection code and results in > `MySQLInputPacket >> initialize` being called too early in `^(self new) > stream: aStream ; initialize` inside of ` MySQLPacket class >> on: aStream`. > It's called automatically on `self new` before the stream is set. I tried to align this semantic to Pharo (as porting from/to Pharo gets easier). Thank you for your analysis! The question is why does the CI pass? Did I by accident not go through authentication? I will try to reproduce and integrate a fix this week. holger _______________________________________________ help-smalltalk mailing list help-smalltalk@gnu.org https://lists.gnu.org/mailman/listinfo/help-smalltalk
