Menu

#26 Split the different message expressions

open
nobody
None
5
2012-08-14
2007-11-08
No

There are some efficiencies to be gained by splitting the
ExpressionMessage and MessageInstruction classes into multiple classes to optimize for the simple single twiddle/no superclass override case.

Discussion

Anonymous
Anonymous

Add attachments
Cancel





Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.