Mikhail, Sorry, I'm a bit slow. From my perspective making a documentation bundle from inter-component interfaces is an excellent idea! I started collecting interfaces from vm/include directory.
Are there any other bundles a community is interested in? Being closer to the point, let me ask if you would be interested in an execution manager documentation bundle? Or do you prefer having it as a part of a JIT documentation bundle? If you vote for a separate bundle, which interface files should I pick for it? There is no vm/em/include directory, so I believe I should take a subset of vm/em/src/*.h files. Also, some inter-component interfaces also should be included, probably the following ones: drlvm/trunk/vm/include/em_intf.h drlvm/trunk/vm/include/open/ee_em_intf.h drlvm/trunk/vm/include/open/em.h drlvm/trunk/vm/include/open/em_profile_access.h drlvm/trunk/vm/include/open/em_vm.h Thanks! On 11/7/06, Mikhail Fursov <[EMAIL PROTECTED]> wrote:
On 07 Nov 2006 19:08:35 +0600, Egor Pasko <[EMAIL PROTECTED]> wrote: > > > > Another problem: anyone who changes a document behaviour must update > > comments too :( > > excuse me, what is "document behaviour"? :) > Read it as 'method/function behaviour'. I mean if you have good comments in file you can't submit a patch with code refactoring without update in comments. Does it become a new requirement? IMO we should start to collect metrics and add comments for intercomponent interfaces only (vm/include/*). -- Mikhail Fursov
-- Thank you, Alexei
