Suggestion to replace use of generics with inheritence in future RM versions

If any developer would do better than a tool, why would anybody write tools in the first place? On Mon, Mar 26, 2012 at 3:26 PM, Thomas Beale < thomas.beale at oceaninformatics.com> wrote: > On 23/03/2012 12:09, Heath Frankel wrote: > >> >> I know every developer can do it better than the next

Suggestion to replace use of generics with inheritence in future RM versions

On 23/03/2012 12:09, Heath Frankel wrote: > > I know every developer can do it better than the next but any > developer can do it better than a tool. > How true. That statement should be on the wall of every UML tool vendor's office! - thomas

Suggestion to replace use of generics with inheritence in future RM versions

Two further variants are now up, with the second containing the more radical changes. Comments welcome.

Suggestion to replace use of generics with inheritence in future RM versions

replace use of generics with inheritence in future RM versions From: serefari...@kurumsalteknoloji.com To: openehr-technical at lists.openehr.org If any developer would do better than a tool, why would anybody write tools in the first place? On Mon, Mar 26, 2012 at 3:26 PM, Thomas Beale

Suggestion to replace use of generics with inheritence in future RM versions

David, This is what I would realistically propose, for the CLUSTER/ELEMENT part of the model. I will also post a

Suggestion to replace use of generics with inheritence in future RM versions

Ok, thanks for the clarification. Heath On 23/03/2012 10:28 PM, "Seref Arikan" wrote: > Hi Heath, > Just to clarify: my original issue is not about auto generation of classes > from XSD, whether or not one choses to do that is irrelevant if the XSD > itself is not supporting generics. The proble

Suggestion to replace use of generics with inheritence in future RM versions

I think the topic has drifted slight from Seref's original issue, although Java nor c# can not implement generics as well as Eiffel or as intended by the spec author it is possible to get close enough to be usable. Similar implementation decisions were necessary when specifying the XML schema and

Suggestion to replace use of generics with inheritence in future RM versions

Hi Heath, Just to clarify: my original issue is not about auto generation of classes from XSD, whether or not one choses to do that is irrelevant if the XSD itself is not supporting generics. The problem is with the XSD (not having support for generics) and it may or may not cascade to programming

Suggestion to replace use of generics with inheritence in future RM versions

yep. Perfectly stated. On 23/03/2012 03:32, pablo pazos wrote: > +1 to Grahame comments. > > - Pablo. > > > Date: Fri, 23 Mar 2012 12:12:04 +1100 > > Subject: Re: Suggestion to replace use of generics with inheritence > in future RM versions > > From: grah

Suggestion to replace use of generics with inheritence in future RM versions

Generally, you can do things in specifications that can't be reproduced in actual implementations. Since there is one specification, but many implementations, the list of things that the specification contains that aren't easy to implement varies widely between implementations. The things that are

Suggestion to replace use of generics with inheritence in future RM versions

David Moner wrote: > I was exaclty thinking about this while seeing this proposal for the > ITEM_STRUCTURE change to a VALUE_CLUSTER: > > http://www.openehr.org/wiki/display/spec/openEHR+2.x+RM+proposals+-+lower+information+model#openEHR2.xRMproposals-lowerinformationmodel-CandidateA.1AddVALUECL

Suggestion to replace use of generics with inheritence in future RM versions

+1 to Grahame comments. - Pablo. > Date: Fri, 23 Mar 2012 12:12:04 +1100 > Subject: Re: Suggestion to replace use of generics with inheritence in future > RM versions > From: grahame at healthintersections.com.au > To: openehr-technical at lists.openehr.org > > Generally,

Suggestion to replace use of generics with inheritence in future RM versions

Shinji KOBAYASHI wrote: > Iterator it = someRmArrayInstance.iterator() > > But I found it must be cut off by 'Occam's razor' in Ruby. > > it = some_rm_array.iterator > > This code looks curious for Java/Eiffel/C# user who are similar to generics, > but it is enough for encapsulated object insta

Suggestion to replace use of generics with inheritence in future RM versions

2012/3/22 Thomas Beale > Instead, I think we should re-invigorate the Java Implementation > Technology Spec, that Rong wrote originally some years ago, to provide Java > implementation guidance for issues like this. All target implementation > technologies have their issues; if we keep hacking th

Suggestion to replace use of generics with inheritence in future RM versions

I should have been more specific. Generics in collections is a managable issue :) and yes, I would not like to go back to non-generic collections either.. On Thu, Mar 22, 2012 at 2:26 PM, Thomas Beale < thomas.beale at oceaninformatics.com> wrote: > > I have to say, software development would be

Suggestion to replace use of generics with inheritence in future RM versions

On 22/03/2012 14:04, Seref Arikan wrote: > I have workarounds for the generics problems in Java, and I would be > more than hapy to contribute them to any doc. I did not know about > Rong's document. > > I think I have made my point, whether or not it is a good one is a > different issue, but I

Suggestion to replace use of generics with inheritence in future RM versions

I have to say, software development would be absolutely dire from my point of view without one particular generic type: Hash. That really would destroy nearly every class I have ever written! - thomas On 22/03/2012 01:47, Shinji KOBAYASHI wrote: > Hi Peter, > > 2012/3/22 Peter Gummer: >> Shinj

Suggestion to replace use of generics with inheritence in future RM versions

On 22/03/2012 13:56, David Moner wrote: > > > 2012/3/22 Thomas Beale > > > Instead, I think we should re-invigorate the Java Implementation > Technology Spec, that Rong wrote originally some years ago, to > provide Java implementation guidan

Suggestion to replace use of generics with inheritence in future RM versions

I have workarounds for the generics problems in Java, and I would be more than hapy to contribute them to any doc. I did not know about Rong's document. I think I have made my point, whether or not it is a good one is a different issue, but I don't want it to be read as an open ended suggestion fo

Suggestion to replace use of generics with inheritence in future RM versions

On 22/03/2012 09:34, Seref Arikan wrote: > Hi Pablo, > I do not want to have a discussion about how to implement specs. That > was not my point. Let me try to be more direct: > > Generics causes problems during implementation of openEHR if Java or > XML is involved. Java + XML has a huge user bas

Suggestion to replace use of generics with inheritence in future RM versions

gestion to replace use of generics with inheritence in future RM versions From: serefari...@kurumsalteknoloji.com To: openehr-technical at lists.openehr.org Hi Pablo, I do not want to have a discussion about how to implement specs. That was not my point. Let me try to be more direct: Generi

Suggestion to replace use of generics with inheritence in future RM versions

Hi Peter, 2012/3/22 Peter Gummer : > Shinji KOBAYASHI wrote: > >> Ruby implementation might be one of the proof for replace of generics. >> I had much struggled to implement generics and got the conclusion >> that we do not need it. > Ruby doesn't have generics at all, right, Shinji? It is right.

Suggestion to replace use of generics with inheritence in future RM versions

Shinji KOBAYASHI wrote: > Ruby implementation might be one of the proof for replace of generics. > I had much struggled to implement generics and got the conclusion > that we do not need it. Ruby doesn't have generics at all, right, Shinji? There's a comparison of generics and inheritance in an

Suggestion to replace use of generics with inheritence in future RM versions

<http://twitter.com/ppazos> > > > Date: Thu, 22 Mar 2012 10:47:37 +0900 > > Subject: Re: Suggestion to replace use of generics with inheritence in > future RM versions > > From: skoba at moss.gr.jp > > To: openehr-technical at lists.?openehr.org > lists.

Suggestion to replace use of generics with inheritence in future RM versions

Hi Seref, Ruby implementation might be one of the proof for replace of generics. I had much struggled to implement generics and got the conclusion that we do not need it. I felt low latency between UK and Japan! However, inheritance could be harmful, because it has too tight restriction for change

Suggestion to replace use of generics with inheritence in future RM versions

dIn: http://uy.linkedin.com/in/pablopazosgutierrez Blog: http://informatica-medica.blogspot.com/ Twitter: http://twitter.com/ppazos > Date: Thu, 22 Mar 2012 10:47:37 +0900 > Subject: Re: Suggestion to replace use of generics with inheritence in future > RM versions > From: skob

Suggestion to replace use of generics with inheritence in future RM versions

Greetings, Looking at the UML page Tom has posted a few minutes ago made me remember something I had in mind for some time. With hope of avoiding any flame wars and attempts to discuss elegance of various approaches in OO approach, may I suggest that the specs use inheritence instead of generics i