Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Fixed
-
None
-
None
-
None
Description
This is a mix of a bug and a task...
classes extending Packet on core client are using a method named getParentString() on the toString();
The initial intent was to be simple and never to abuse inheritance on the getParentString();
Recent iteration on the code added a few occasions with toString() calling getParentString() calling toString() what caused a recursive loop.
I'm making this simpler. by introducing a getPacketString() on PacketImpl where every extension of PacketImpl to simply call super.getParentString();
Even though it still possible for someone to call itself on getParentString(), at least it would be clearer and easier to catch on revisions.
Attachments
Issue Links
- links to