Re: [Oorexx-devel] Move Windows specific classes out of rexxref?

[John B. <joh...@in...>]

Now I'm even more confused.  I look at "built-in" stuff as being built-in to
the product (comes with the product).  Having to include a requires
directive, to me, is just the way it was implemented.  I don't think I
should have to know whether a class requires a requires directive ahead of
time so I'll know which book to look in.

Personally, I thought the purpose of splitting it out was because it was
platform specific.  If that is the case, I thought everything platform
specific would go.  That way, I would know that if it's a windows thing I
wanted to look up, don't look in the reference.

It's much easier to know that something is platform specific than to know
that the implementation of something in really "built-in".

Thanks,

John
-----Original Message-----
From: Mark Miesfeld [mailto:mie...@gm...] 
Sent: Saturday, February 07, 2009 10:12 PM
To: Open Object Rexx Developer Mailing List
Subject: Re: [Oorexx-devel] Move Windows specific classes out of rexxref?

On Sat, Feb 7, 2009 at 3:54 PM, John Bodoh <joh...@in...> wrote:

> If the purpose is to isolate platform specific functionality, does this
> include the utilities of different platforms like Windows, AIX, UNIX,
> Solaris?

John,

Just to be sure we are clear here, this has nothing to do with the
actual classes, just the documentation.

The purpose, as I see it, is to move section 5.5, titled "Windows
Specific Classes" out of chapter 5, titled "The Builtin Classes."
Because, the Windows specific classes are *not* builtin classes.

Then, having decided to move that part of the documentation, you have
to ask, does that documentation even belong in the ooRexx Reference
book?  Since the rest of the ooRexx Reference is pretty much platform
agnostic, Rick's and my answer is no.

It doesn't have any thing to do with the RexxUtils documentation
either.  That documentation will always stay together, with the
functions that are platform specific being noted.  So things in the
RexxUtil documentation chapter like SysIni will always be in that
chapter, because SysIni is part of the whole package.

--
Mark Miesfeld

----------------------------------------------------------------------------
--
Create and Deploy Rich Internet Apps outside the browser with
Adobe(R)AIR(TM)
software. With Adobe AIR, Ajax developers can use existing skills and code
to
build responsive, highly engaging applications that combine the power of
local
resources and data with the reach of the web. Download the Adobe AIR SDK and
Ajax docs to start building applications today-http://p.sf.net/sfu/adobe-com
_______________________________________________
Oorexx-devel mailing list
Oor...@li...
https://lists.sourceforge.net/lists/listinfo/oorexx-devel