<flame> Hey Tim Isn't using lack of multiple inheritance as a criteria going to seriously restrict your choice of language? C#, Java, etc - none of the contemporary framework languages use multiple inheritance. Were you thinking of coding in C++? :)
</flame> Seriously, Ruby is probably a fine language for implementing openEHR. IANARL, but it's quite a sophisticated little language and it's not hard to appreciate the "feel" of the frameworks that use it - particularly the "don't repeat yourself" maxim of the Rails framework. I can't imagine there'd be a compelling reason not to use Ruby, if that happened to be your language of choice. Just my opinion. *chuckle* Cheers Tom -----Original Message----- From: Tim Cook [mailto:[email protected]] Sent: Friday, 3 February 2006 3:54 AM To: openehr-technical at openehr.org Subject: Re: experience / opinions On Thu, 2006-02-02 at 10:01 -0600, Bill Walton wrote: > Does anyone have any experience with / opinions about the suitability > of Ruby and Rails as implementation platforms for openEHR? > Some of us always have opinions. ;-) I think the biggest drawback in using Ruby is the lack of multiple inheritance. However, Ruby lovers will argue that using mixin classes can achieve the same thing and that multiple inheritance is a source of confusion. I *do* think it makes sense to use existing, tried and tested frameworks/components as part of an infrastructure where possible. Cheers, -- Tim Cook
