My point wasn't about how genetics affect behaviour. There are way to many variables in play there. My point was that even identical twins, who have identical genes, can appear different: variations in height, build, finger prints, freckle patterns, aptitudes, etc.
They are clones, appear similar, but are not the same, even on physical appearance.
I don't think this is news to biologists, or cognitive scientists.
Genes play a part, but nurture plays a part two. The proof is sitting in plain sight. Identical twins are genetically identical: they are naturally occurring human clones. However, identical twins are also different people. They share some traits, but still are very different. And identical twins also share a lot of their environment: a clone (a clearer term: "identical twin shifted in time", ITSIT?) will have less common environment, and hence be likely to be more different.
I'd agree. The book is excellent, covers string processing in depth, and has the best explanation of dynamic programming (a *very* useful technique) that I have come across. It is rather heavy, but it is worth the effort.
I'd agree. DocBook is excellent, and comprehensive. It is designed for applications like this (technical documentation, etc.), is well supported (built into all ArborText's editors, Frame+SGML, etc.). It is well documented: it has an O'Reilly book written by Norman Walsh. It is very easy to add support for it into stanard text editors: I use xemacs and it works fine (no flames please).
Linking features between documents can be achieved using <olink> and <ulink> tags. The exact details would depend on your repository setup, but the things you want to do are catered for.
Hopefully M$ have implemented this as a Body/Handler pattern for the file system, i.e., if the user edits one of the linked files, that the now different file is unlinked and becomes its own separate file. This would allow you to have backups that didn't change with the original sources.
However, there is a performance hit for this if the linked objects change a lot. Java Strings are implemented as an instance of the Body/Handler, and string manipulation is much slower using Strings than StringBuffers/char arrays.
Slashdot Mirror
My point wasn't about how genetics affect behaviour. There are way to many variables in play there. My point was that even identical twins, who have identical genes, can appear different: variations in height, build, finger prints, freckle patterns, aptitudes, etc.
They are clones, appear similar, but are not the same, even on physical appearance.
I don't think this is news to biologists, or cognitive scientists.
Genes play a part, but nurture plays a part two. The proof is sitting in plain sight. Identical twins are genetically identical: they are naturally occurring human clones. However, identical twins are also different people. They share some traits, but still are very different. And identical twins also share a lot of their environment: a clone (a clearer term: "identical twin shifted in time", ITSIT?) will have less common environment, and hence be likely to be more different.
I'd agree. The book is excellent, covers string processing in depth, and has the best explanation of dynamic programming (a *very* useful technique) that I have come across. It is rather heavy, but it is worth the effort.
I'd agree. DocBook is excellent, and comprehensive. It is designed for applications like this (technical documentation, etc.), is well supported (built into all ArborText's editors, Frame+SGML, etc.). It is well documented: it has an O'Reilly book written by Norman Walsh. It is very easy to add support for it into stanard text editors: I use xemacs and it works fine (no flames please).
Linking features between documents can be achieved using <olink> and <ulink> tags. The exact details would depend on your repository setup, but the things you want to do are catered for.
Best of luck.
PrintStream o = System.out;
o.print("foo");
o.print("anything...");
/* etc. */
Hopefully M$ have implemented this as a Body/Handler pattern for the file system, i.e., if the user edits one of the linked files, that the now different file is unlinked and becomes its own separate file. This would allow you to have backups that didn't change with the original sources.
However, there is a performance hit for this if the linked objects change a lot. Java Strings are implemented as an instance of the Body/Handler, and string manipulation is much slower using Strings than StringBuffers/char arrays.