[Pharo-project] ClassFactoryForTestCase
Would it be fine if ClassFactoryForTestCase would silently create classes? First of all, that class is awesome! However, it is sloooooow. It creates classes that are logged to the entire system, and when cleaning up goes to the length of cleaning up the log files. Creating anonymous classes would be faster. So I have two questions - Any known users of that class that require the logging? - What are the gotchas of anonymous classes? cheers, AA -- 4th Workshop on Dynamic Languages and Applications Submit papers by March 31, 2010. http://bit.ly/dyla2010
Follow up. Why is #compile: not silent? The method is only ever used in tests, where (as I would expect) logging of compilations is not what you want. --AA PS: I know there is #compileSilently:classified:notifying:, but if we know that compilation *without* classification and notification is only ever used in tests, why not pick the shortest possible name fro that so our tests are more readable?
because there is compile:Silently: and because the compiler is old but working. On Dec 23, 2009, at 11:22 PM, Adrian Kuhn wrote:
Follow up.
Why is #compile: not silent? The method is only ever used in tests, where (as I would expect) logging of compilations is not what you want.
--AA
PS: I know there is #compileSilently:classified:notifying:, but if we know that compilation *without* classification and notification is only ever used in tests, why not pick the shortest possible name fro that so our tests are more readable?
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
participants (2)
-
Adrian Kuhn -
Stéphane Ducasse