How about including them (for completeness) in the reference with just a "pointer" to the guide where the full documentation would be included?
Rick McGuire wrote: > I'm trying to figure out how the Pointer and Buffer classes should be > documented. These are Rexx classes, but they really only exist for > the benefit of authors of native libraries. For the most part, > "normal" users of ooRexx will never see an instance of these classes > and won't even know they exist. For that reason, I'm reluctant to > include these in the utility classes section because it will be very > difficult to document these outside of the context of the APIs and how > the APIs work. At the same time, you sort of need to understand these > are real ooRexx classes when using the API documentation, so it makes > sense that these classes should be part of the programmer's guide, not > in the reference. I'm interested in how others feel about these two > classes. > > Rick > > ------------------------------------------------------------------------- > This SF.Net email is sponsored by the Moblin Your Move Developer's challenge > Build the coolest Linux based applications with Moblin SDK & win great prizes > Grand prize is a trip for two to an Open Source event anywhere in the world > http://moblin-contest.org/redirect.php?banner_id=100&url=/ > _______________________________________________ > Oorexx-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/oorexx-devel > > -- Gil Barmwater ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Oorexx-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/oorexx-devel
