>
> enhancements get set to a "pending" with a milestone indicating which
> release they will be in
>
Ok, thanks. I have set the status for two RFE's back to "pending".
Would you suggest to also keep doc bugs as "pending" ? (I have set a few
ones to "closed" after my commit)
Erich
On Fri, May 22, 2015 at 8:34 PM, Rick McGuire <[email protected]> wrote:
> Erich,
>
> You might not want to make these closed status quite yet. We found over
> the years that in order to keep track of what is going to be in a future
> release, enhancements get set to a "pending" with a milestone indicating
> which release they will be in. Once the release ships, these tickets get
> set to "closed". This makes it easier to sort out which things are in the
> release and what state they are in.
>
> Rick
>
> ---------- Forwarded message ----------
> From: Erich <[email protected]>
> Date: Fri, May 22, 2015 at 2:29 PM
> Subject: [oorexx:feature-requests] #654 Add an instruction that is the
> inverse of EXPOSE
> To: "[oorexx:feature-requests]" <[email protected]>
>
>
> - **status**: accepted --> closed
>
>
>
> ---
>
> ** [feature-requests:#654] Add an instruction that is the inverse of
> EXPOSE**
>
> **Status:** closed
> **Milestone:** 5.0.0
> **Created:** Wed Oct 29, 2014 01:02 PM UTC by Rick McGuire
> **Last Updated:** Fri May 22, 2015 06:23 PM UTC
> **Owner:** Erich
>
> This sort of comes from SmallTalk, where methods declare the local
> variables and all other variables are object variables. ooRexx uses the
> opposite approach, where object variables must be specified using EXPOSE
> and all other variables are local. For some methods, like INIT methods, it
> would be nice to use the opposite approach. For example, in an init method
> that initializes a number of attributes, one needs to make the decision
> between listing a large set of variables on expose vs. using the slower
> self~attributeName assignment forms. It would be nice if there were a
> mechanism that allowed everything to default to object variables. The USE
> instruction might work well for this since the operation is keyword based
> and it was always intended to be a multi-purpose instruction.
>
> ::method init
> USE LOCAL x y z
>
> The variable list should be optional to specify that everything is an
> object variable.
>
> ::method init
> use local -- everything is an object variable.
>
>
>
> ---
>
> Sent from sourceforge.net because you indicated interest in <
> https://sourceforge.net/p/oorexx/feature-requests/654/>
>
>
>
> To unsubscribe from further messages, please visit <
> https://sourceforge.net/auth/subscriptions/>
>
>
>
> ------------------------------------------------------------------------------
> One dashboard for servers and applications across Physical-Virtual-Cloud
> Widest out-of-the-box monitoring support with 50+ applications
> Performance metrics, stats and reports that give you Actionable Insights
> Deep dive visibility with transaction tracing using APM Insight.
> http://ad.doubleclick.net/ddm/clk/290420510;117567292;y
> _______________________________________________
> Oorexx-devel mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/oorexx-devel
>
>
------------------------------------------------------------------------------
One dashboard for servers and applications across Physical-Virtual-Cloud
Widest out-of-the-box monitoring support with 50+ applications
Performance metrics, stats and reports that give you Actionable Insights
Deep dive visibility with transaction tracing using APM Insight.
http://ad.doubleclick.net/ddm/clk/290420510;117567292;y
_______________________________________________
Oorexx-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/oorexx-devel
