About the following: >I think that README and "Porting Layer description" should have >different content. README contains directory structure and "How to >use" hints. Description should overview architecture and relationship >with other components.
I agree that the directory structure needn't be posted to the website, but I think there's nothing wrong about "how-to hints" in an easily accessible place on the site :) anyway, right now my environment has collapsed, so I cannot build the website. Sorry for the inconvenience, I'll have a draft of the porting posted tomorrow. On Fri, Apr 25, 2008 at 1:24 PM, Andrey Yakushev <[EMAIL PROTECTED]> wrote: > On 4/24/08, Alexey Varlamov <[EMAIL PROTECTED]> wrote: > > 2008/4/24, Nadya Morozova <[EMAIL PROTECTED]>: > > > And a side question: are we ok with having the info in the source code? > > > should i move the info to the website? > > > > IMO this should be consistent in the first place; as we have most > > other docs on site, this one better be moved there too. Moreover > > Developer's Guide refers to missing "Porting Layer description > > document" - probably this one was meant. > > OTOH I must admit the doc is somewhat scrappy yet, not really > informative. > > > > I think that README and "Porting Layer description" should have > different content. README contains directory structure and "How to > use" hints. Description should overview architecture and relationship > with other components. > > > > > > > On Thu, Apr 24, 2008 at 1:49 PM, Nadya Morozova < > [EMAIL PROTECTED]> > > > wrote: > > > > > > > Alexey, > > > > Could you please log the outdated bits to the JIRA issue? I got the > info > > > > from Andrey Y., and he seemed well-informed on the current > implementation. > > > > Probably, between creating the patch and its commit, the code has > changed :) > > > > If you were more specific at what needs to be changed, we can do so > quickly. > > > > I know I was not very constructive in that comment, so already > > committed a quick fix at r651210. > > Thanks for that. I really didn't read all the text, only changed parts. > > > > > > > About the crash handler, I think we have a fresh document: Universal > Crash > > > > and Signals Handler at > > > > http://harmony.apache.org/subcomponents/drlvm/crash_handler.html. > > > > I overlooked this one, thanks! > > (and static menu sucks, especially when browsing documentation :( ) > > > > Regards, > > Alexey > > > > > > > > > > > > - nadya > > > > > > > > > > > > > > > > On Thu, Apr 24, 2008 at 1:17 PM, Alexey Varlamov < > > > > [EMAIL PROTECTED]> wrote: > > > > > > > > > Oh, most contents of the 1st section (Design Notes) is vastly > > > > > outdated. E.g. we do not mask APR API with port_* macros anymore, > and > > > > > so on. > > > > > BTW, would be nice to get an addition for signal/crash handling > pieces > > > > > which also were added this year... > > > > > -- > > > > > Alexey > > > > > > > > > > > > > > > 2008/4/24, Nadya Morozova <[EMAIL PROTECTED]>: > > > > > > HI all, > > > > > > Thanks to Andrey Yakushev's patch [1] we now have an updated > README > > > > > file > > > > > > that goes with the Porting module [2]. The document describes the > > > > > current > > > > > > approach to using APR and extensions for porting DRLVM. > > > > > > Your reviews and additions to documentation are most welcome. > > > > > > > > > > > > NOTE: the document is still incomplete, we're missing a > description of > > > > > > platforms defines and macros. Any volunteers? > > > > > > > > > > > > [1] https://issues.apache.org/jira/browse/HARMONY-5736 > > > > > > [2] > > > > > > > > > > > > http://svn.apache.org/viewvc/harmony/enhanced/drlvm/trunk/vm/port/doc/PortReadme.htm > > > > > > -- > > > > > > Cheers, > > > > > > Nadya > > > > > > > > > > > > > > > > > > > > > > > > > > > -- > > > > Cheers, > > > > Nadya > > > > > > > > > > > > > > > -- > > > Cheers, > > > Nadya > > > > > > > > -- > Thanks, > Andrey > -- Cheers, Nadya
