On 11/03/2012 09:43, Thomas Beale wrote: > > Well, this is the HL7 modelling mentality, trying to create a data > type or class with all possible attributes, some of which can be > removed in some subclass. This is bad modelling, we should not be > doing it. I'm talking about interfaces here, although, having looked > into all the major languages I didn't find any that didn't have > distinct date, time, date/time and duration types, so even in > implementations, I could not see the point.
apparently I was wrong about C# (still stuck with only one DateTime type), but I checked on Java (Joda <http://joda-time.sourceforge.net/>), Python (date/time lib <http://docs.python.org/library/datetime.html>), Ruby (date/time lib <http://www.ruby-doc.org/stdlib-1.9.3/libdoc/date/rdoc/index.html>)... all have separate types. * * - thomas -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.openehr.org/pipermail/openehr-technical_lists.openehr.org/attachments/20120312/1f2e71c2/attachment.html>
