On 22.02.2017 15:44, Rick McGuire wrote:
>
>
> On Wed, Feb 22, 2017 at 9:33 AM, Rony G. Flatscher <rony.flatsc...@wu.ac.at
> <mailto:rony.flatsc...@wu.ac.at>> wrote:
>
> O.K., this may be a little bit weird: I can manage to have the test code
> run without an
> exception, repeatedly!
>
> Background: in the native code I have many, many output statements to
> stderr for debugging
> (tons over the years, controlled by defines) in the form of, e.g:
>
> fprintf(stderr, "...\t\t\t\t\targ(%d)=[%s]\n", idx,
> rtc->CString(rtc->SendMessage0(rtc->ArrayAt(ra,idx),"STRING")));
> fflush(stderr);
>
> Changing the above output to:
>
> fprintf(stderr, "...\t\t\t\t\targ(%d)=[%*.64*s]\n", idx,
> rtc->CString(rtc->SendMessage0(rtc->ArrayAt(ra,idx),"STRING")));
> fflush(stderr);
>
> makes the test code run it seems!
>
> btw, thjis is also going to add two entries to the local reference table each
> time you do this.
> The table could end up getting quite large if you have a long running call.
> If you're only doing
> this for debug purposes, it probably doesn't matter.
Yes, it is for debugging only. ---rony
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
_______________________________________________
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel
