While looking into this in order to create an easy to use test case, employing
now ooRexx 4.1.1
beta, the problem with ObjectToStringValue() cannot be recreated anymore.
---rony
On 09.02.2012 13:13, Rony G. Flatscher wrote:
> While debugging new code I stumbled over the following observation:
>
> 1. fetching a RexxObjectPtr from .local with:
> bsfClz=rtc->SendMessage0(rtc->GetLocalEnvironment(), "BSF");
>
> 2. getting the string representation (for debugging) of that ooRexx class
> object works with:
> rtc->CString(rtc->SendMessage0(clzBSF,"STRING"));
>
> 3. whereas the following causes a crash:
> rtc->CString(rtc->SendMessage0(clzBSF,"MAKESTRING"));
>
> 4. whereas the following causes a crash:
> const char *str=rtc->ObjectToStringValue(clzBSF);
>
> 5. whereas the following causes a crash:
> const char *str=rtc->CString(rtc->ObjectToString(clzBSF));
>
> As sending messages to "bsfClz" works reliably, I can proceed with my work,
> however, I wonder why
> sending "MAKESTRING" or invoking the APIs ObjectToStringValue() and
> ObjectToString() in this
> scenario might cause a crash in native code?
>
> TIA,
>
> ---rony
------------------------------------------------------------------------------
Virtualization & Cloud Management Using Capacity Planning
Cloud computing makes use of virtualization - but cloud computing
also focuses on allowing computing to be delivered as a service.
http://www.accelacomm.com/jaw/sfnl/114/51521223/
_______________________________________________
Oorexx-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/oorexx-devel
