[.net] class library using internal classes

Started by
10 comments, last by joanusdmentia 19 years, 3 months ago
Take a look at the Factory design pattern.

Design patterns are to solve problems like this one.

Cheers
Advertisement
Err....I fail to see how the factory pattern has anything to do with his problem. The factory pattern is for creating types at runtime without knowing the full type information, the base interface for the types (ie. IGraphics, IWindow, etc.) would still need to be public leaving him in exactly the same situation.

But yes, design patterns are generally a Good Thing.
"Voilà! In view, a humble vaudevillian veteran, cast vicariously as both victim and villain by the vicissitudes of Fate. This visage, no mere veneer of vanity, is a vestige of the vox populi, now vacant, vanished. However, this valorous visitation of a bygone vexation stands vivified, and has vowed to vanquish these venal and virulent vermin vanguarding vice and vouchsafing the violently vicious and voracious violation of volition. The only verdict is vengeance; a vendetta held as a votive, not in vain, for the value and veracity of such shall one day vindicate the vigilant and the virtuous. Verily, this vichyssoise of verbiage veers most verbose, so let me simply add that it's my very good honor to meet you and you may call me V.".....V

This topic is closed to new replies.

Advertisement