Rick McGuire wrote:
I was sort of thinking the same thing.

Rick

On Mon, Jan 5, 2009 at 10:51 AM, Mark Miesfeld <miesf...@gmail.com> wrote:
On Mon, Jan 5, 2009 at 7:38 AM, David Ashley <david.ashley....@gmail.com>

I have started entering the new oo apis into the rexxpg document. They
are in Appendix A (the classic apis have been moved to Appendix B). I
would really appreciate some feedback on the style. You can download it at

http://build.oorexx.org/builds/release_candidates/
David,

I had built the doc a couple of days ago (before your recent update.)
I just had one question / thought.

Should the doc be in an appendix?  Or should it be in regular chapters
of the document?

Probably a trivial thing in the over-all scheme of things.  Maybe a
result of my own personal blind spots.  I always think of appendices
as the not-so-important thrown in as an afterthought stuff.

--
Mark Miesfeld

------------------------------------------------------------------------------
_______________________________________________
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel


------------------------------------------------------------------------------
_______________________________________________
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel

I also can agree with this idea. I was just carrying forward with what had come previously. The classic apis were in an appendix therefore I put the oo apis in an appendix. At one time I questioned the placement of the classic apis in the appendix but I never got around to doing anything about it :-)

So I guess the question becomes should the classic apis also be moved to a chapter and out of the appendix?

David Ashley

------------------------------------------------------------------------------
_______________________________________________
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel

Reply via email to