On Sun, Jul 6, 2014 at 12:31 PM, Sahananda (Jon) Wolfers <
[email protected]> wrote:
> Hi Rick,
>
> I searched the RFEs and found #140
> <http://sourceforge.net/p/oorexx/feature-requests/140/> which requests
> something like this and in the reason for rejection you explain the
> difference between the original name and the registration name.
>
> I sounds like to be useful, we would need a method for each, but perhaps
> this is not that easy to do. I'm a little bit out of my depth here, but I
> assume that if the method or routine were got up from a directive in a
> script, then in every case the original name would equal the registration
> name, and it is just the primitive classes where they might differ. Is
> that correct?
>
> No, that is not correct. Even if a method is created by a directive, it
can be added to a class or object via a different name. The internal name
of the method really doesn't have any real significance other than a
historical one. With 20-20 hindsight, I would never have been done that
way.
> I would like some guidance here on the list, because opening an RFE so
> similar to a rejected one would probably cause justified irritation.
>
Yeah, I probably jumped the gun on the name part. There are even ways that
methods can get created without the internal name.
Rick
>
> thanks,
> Jon
>
>
> On 4 July 2014 22:44, Rick McGuire <[email protected]> wrote:
>
>> Wow, I would have assumed that was there already. Sounds like you should
>> open an RFE for this. But note that the name the object has is not
>> necessarily the same as the name it was called under.
>>
>> Rick
>>
>>
>> On Fri, Jul 4, 2014 at 5:06 PM, Sahananda (Jon) Wolfers <
>> [email protected]> wrote:
>>
>>> I would value a separate method for the name of the routine or method. I
>>> would be happy to parse it out of the directive line text or perhaps it
>>> should have it's own separate method.
>>> Jon
>>> On Jul 4, 2014 12:35 PM, "Rony G. Flatscher" <[email protected]>
>>> wrote:
>>>
>>>>
>>>> On 04.07.2014 12:33, Rick McGuire wrote:
>>>>
>>>> ... cut ...
>>>>
>>>> > Another option would be to add a separate method to get the directive
>>>> source line. That is a
>>>> > little more work, but also doable. The advantage of doing that is
>>>> the information would also be
>>>> > there for native routines and methods. Actually, now that I write
>>>> that, I think I'm starting to
>>>> > lean in that direction. Anyway, I'd like some opinions on this.
>>>> +1
>>>>
>>>> ---rony
>>>>
>>>>
>>>> ------------------------------------------------------------------------------
>>>> Open source business process management suite built on Java and Eclipse
>>>> Turn processes into business applications with Bonita BPM Community
>>>> Edition
>>>> Quickly connect people, data, and systems into organized workflows
>>>> Winner of BOSSIE, CODIE, OW2 and Gartner awards
>>>> http://p.sf.net/sfu/Bonitasoft
>>>> _______________________________________________
>>>> Oorexx-devel mailing list
>>>> [email protected]
>>>> https://lists.sourceforge.net/lists/listinfo/oorexx-devel
>>>>
>>>
>>>
>>> ------------------------------------------------------------------------------
>>> Open source business process management suite built on Java and Eclipse
>>> Turn processes into business applications with Bonita BPM Community
>>> Edition
>>> Quickly connect people, data, and systems into organized workflows
>>> Winner of BOSSIE, CODIE, OW2 and Gartner awards
>>> http://p.sf.net/sfu/Bonitasoft
>>> _______________________________________________
>>> Oorexx-devel mailing list
>>> [email protected]
>>> https://lists.sourceforge.net/lists/listinfo/oorexx-devel
>>>
>>>
>>
>>
>> ------------------------------------------------------------------------------
>> Open source business process management suite built on Java and Eclipse
>> Turn processes into business applications with Bonita BPM Community
>> Edition
>> Quickly connect people, data, and systems into organized workflows
>> Winner of BOSSIE, CODIE, OW2 and Gartner awards
>> http://p.sf.net/sfu/Bonitasoft
>> _______________________________________________
>> Oorexx-devel mailing list
>> [email protected]
>> https://lists.sourceforge.net/lists/listinfo/oorexx-devel
>>
>>
>
>
> ------------------------------------------------------------------------------
> Open source business process management suite built on Java and Eclipse
> Turn processes into business applications with Bonita BPM Community Edition
> Quickly connect people, data, and systems into organized workflows
> Winner of BOSSIE, CODIE, OW2 and Gartner awards
> http://p.sf.net/sfu/Bonitasoft
> _______________________________________________
> Oorexx-devel mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/oorexx-devel
>
>
------------------------------------------------------------------------------
Open source business process management suite built on Java and Eclipse
Turn processes into business applications with Bonita BPM Community Edition
Quickly connect people, data, and systems into organized workflows
Winner of BOSSIE, CODIE, OW2 and Gartner awards
http://p.sf.net/sfu/Bonitasoft
_______________________________________________
Oorexx-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/oorexx-devel
