Hi guys Iâm trying to understand freeType and when I debug I get aBlah aFoo and this is frankly annoying because Iâm trying to learn the implementation and it does not help me at all. I hate the classes that only their implementors understand. In Pharo 4.0 I will put a strict rule: - no class will be integrated if they do not redefine printOn: - I will set a general rules to check printOn: methods. printOn: methods are the first debugging information. Stef
I am all for that, but I don't think you can make it that strict, what if there are no instance variables ? I like custom #printOn:'s especially for debugging. On 28 Mar 2014, at 21:45, Pharo4Stef <pharo4Stef@free.fr> wrote:
Hi guys
Iâm trying to understand freeType and when I debug I get aBlah aFoo and this is frankly annoying because Iâm trying to learn the implementation and it does not help me at all.
I hate the classes that only their implementors understand. In Pharo 4.0 I will put a strict rule: - no class will be integrated if they do not redefine printOn: - I will set a general rules to check printOn: methods.
printOn: methods are the first debugging information.
Stef
On 28 Mar 2014, at 22:08, Sven Van Caekenberghe <sven@stfx.eu> wrote:
I am all for that, but I don't think you can make it that strict, what if there are no instance variables ?
ok :) a smart rule
I like custom #printOn:'s especially for debugging.
On 28 Mar 2014, at 21:45, Pharo4Stef <pharo4Stef@free.fr> wrote:
Hi guys
Iâm trying to understand freeType and when I debug I get aBlah aFoo and this is frankly annoying because Iâm trying to learn the implementation and it does not help me at all.
I hate the classes that only their implementors understand. In Pharo 4.0 I will put a strict rule: - no class will be integrated if they do not redefine printOn: - I will set a general rules to check printOn: methods.
printOn: methods are the first debugging information.
Stef
participants (2)
-
Pharo4Stef -
Sven Van Caekenberghe