I seem to be a minority here. I'm all for name:namespace. The reasoning is: you want a behaviour, the secondary thought is in which environment, the normal environment being ooRexx, not requiring the namespace extension. While in the namespace:name you would have to find out in which environment you are, when you don't have control over in which environment you are running.
A little like ADDRESS to change where you want to go your external commands to go to. I could live with the other way around, but not wholehearedly. On 1-10-2014 16:49, u.zinngr...@inter.nl.net wrote: > Op Wo, oktober 1, 2014 15:21 schreef Rick McGuire: > >>> The deeper I get into the details of implementing this, the more I >>> think it needs to be "namespace;name" too. > Also C++ uses namespace::name. > Is C++ a sensible argument to consider a double colon, like > > x = rexx::array~new > > ? > >>>> ::requires 'some.file' namespace somename >>>> >>>> >>>> Once a requires file has been tagged with a namespace name, it can be >>>> used to qualify references to classes within that namespace explicitly >>>> identify which version you want. > May 'some.file' already contain namespaces othername, furthername ? > Could this, like in C++, be expressed by a hierarchy > > x = somename:othername:array~new > > ? > >>>> ::requires 'some.file' namespace somename > Do implicit namespaces make sense ? e.g. > > ::requires 'some.file' > > would be equivalent to > > ::requires 'some.file' namespace 'some.file' > > > >>>> As part of this, there is a special >>>> reserved namespace of REXX that will allow you to always get to the >>>> interpreter-provided version of things. >> x = rexx:array~new >> >> You can always get access to the system classes using the REXX namespace, >> regardless of what has been added to the environment or defined in >> packages you might include. > Can this functionality be provided without a name that user might use ? > > x = :array~new > or > x = .:array~new > or > x = .array~new > > ? > > Last, one might want to switch the default namespace to save on typing. > This would require a distinction between a current and the REXX namespace > plus a command to change the current namespace, maybe > > address namespace newnamespace > > or some other syntax. > > > Cheers, Uli > > > > ------------------------------------------------------------------------------ > Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer > Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports > Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper > Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer > http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk > _______________________________________________ > Oorexx-devel mailing list > Oorexx-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/oorexx-devel -- Ruurd Idenburg ------------------------------------------------------------------------------ Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk _______________________________________________ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
