William Hindman
wdhindman at dejpolsystems.com
Thu Feb 26 13:30:29 CST 2009
...with every step forward there are new problems that have to be resolved ..."no no no no no" would still have us wearing fig leaves :( William -------------------------------------------------- From: "Salakhetdinov Shamil" <mcp2004 at mail.ru> Sent: Thursday, February 26, 2009 2:08 PM To: "Access Developers discussion and problem solving" <accessd at databaseadvisors.com> Subject: Re: [AccessD] Class costs & benefits > > Hi Arthur, > > Have a look - Ruby has multiple inheritance features implememted using so > called Mix-ins to effectively solve the issue you mentioned: > > http://www.artima.com/intv/tuesday2.html > > I'd bet C# and VB.NEt will follow this pattern or something like that in > the future versions (but not yet in next versions C#4.0 and VB10 (VBx))... > > Thank you. > > -- > Shamil > > -----Original Message----- > From: Arthur Fuller <fuller.artful at gmail.com> > To: Access Developers discussion and problem > solving<accessd at databaseadvisors.com> > Date: Thu, 26 Feb 2009 13:01:27 -0500 > Subject: Re: [AccessD] Class costs & benefits > >> No no no no no, I interject. Multiple inheritance has been deemed >> problematic in virtually language that offered it. It is simply too crazy >> a >> construct for mere mortals such as myself to handle. For example, suppose >> that I inherit from both class A and B, and each has a method of the same >> name. How to distringuish which one you want? This path IMO leads to nuts >> documentation and nuts programming. Even the C++ guys have abandoned this >> approach. >> >> A. >> -- >> AccessD mailing list >> AccessD at databaseadvisors.com >> http://databaseadvisors.com/mailman/listinfo/accessd >> Website: http://www.databaseadvisors.com >> > > -- > AccessD mailing list > AccessD at databaseadvisors.com > http://databaseadvisors.com/mailman/listinfo/accessd > Website: http://www.databaseadvisors.com >