A Web-based News Reader
| Subject | mixins rock | |||||||||||||||||||||||||||
| From | Ben Hinkle <bhinkle4@juno.com> | |||||||||||||||||||||||||||
| Date | Thu, 09 Sep 2004 22:44:25 -0400 | |||||||||||||||||||||||||||
| Newsgroups | digitalmars.D | |||||||||||||||||||||||||||
Here I thought mixins were a pain but I've been going through mintl and experimenting with consolidating shared code into mixins and they've been working great. I'd like to really say thanks to Walter for adding mixins. I wasn't convinced before but I'm really liking them now. In my sandbox mintl now has three mixins: - one for opCat-like functions (6 functions) - one for opApply overloads and variations (8 functions) - one for backwards opApply and toSeq variations (5 functions) They cut way down on the cut-and-paste aspect of mintl that had been bothering me. It's to the point where there isn't any "boilerplate" code in the individual containers. I've found using public mixins to be more successful that using private mixins. Private symbols seem to trip up mixins. The rules are probably obvious but I haven't taken the time to figure them out so I've gotten in the habit of only mixing in public declarations and having the mixins only reference public symbols. -Ben | ||||||||||||||||||||||||||||
| ||||||||||||||||||||||||||||
mixins rock (Current message)
