On Tue, Jun 23, 2009 at 3:10 AM, Rony G.
Flatscher wrote:
> It seems that ooRexx 4.0 removed the necessity of placing ::Requires
> directives before any other directive. Two questions:
>
> Is this intended?
Yes, the restriction was artificial and has been removed.
> If intended, is the behaviour like this? If not, what is the specified
> behaviour (I could not find the respective documentation, but then, I may
> just have missed it)
There is no relationship between the placement of the ::requires
directive within the file and the usage of
any symbols imported by the directive. The ::requires directives are
processed before any other
directives, so all of the classes will be visible. This is the same
bahavior as the past.
>
> The public and classes routines defined in a file "A" that gets ::Requires
> can be referred to by the immediately following ::Class, ::Method and
> ::Routine directives.
> If another file "B" gets required thereafter, the immediately following
> ::Class, ::Method and ::Routine directives would refer to "B"s public
> classes and routines in the case that there are name clashes with once
> defined in file "A".
>
> ---rony
>
>
> --
> Are you an open source citizen? Join us for the Open Source Bridge
> conference!
> Portland, OR, June 17-19. Two days of sessions, one day of unconference:
> $250.
> Need another reason to go? 24-hour hacker lounge. Register today!
> http://ad.doubleclick.net/clk;215844324;13503038;v?http://opensourcebridge.org
> ___
> Oorexx-devel mailing list
> Oorexx-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/oorexx-devel
>
>
--
Are you an open source citizen? Join us for the Open Source Bridge conference!
Portland, OR, June 17-19. Two days of sessions, one day of unconference: $250.
Need another reason to go? 24-hour hacker lounge. Register today!
http://ad.doubleclick.net/clk;215844324;13503038;v?http://opensourcebridge.org
___
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel
