Alan Condit wrote: >I think that I may have found a bug in the interpreter (at the very >least a problem). > >This call works to call (indirect) o600 from within o<CallSubSub> >o<CallSubSub> call [600] [-0.1161] [-0.0062] >However, if you change to named o-words, then this call reports a bad >number format (since it is not a number but the name of the >subroutine to be called). >o<CallSubSub> call [<CutOutside>] [-0.1161] [-0.0062] > >Is this a bug? Is there a work around at the moment? > > This isn't a bug, and there is no workaround as far as I know.
The issue is that variables are numbers, not text strings. You can indirectly call a numbered subroutine because the variable is converted into a number before the call is made, and the interpreter expects a number for a subroutine call (names were only added in the last year or two). The only way to make this work the way I'm thinking you want it to work is to add the ability for variables to contain strings. This would be a nice feature, but I'm not sure how hard it is to add. - Steve ------------------------------------------------------------------------------ Crystal Reports - New Free Runtime and 30 Day Trial Check out the new simplified licensing option that enables unlimited royalty-free distribution of the report engine for externally facing server and web deployment. http://p.sf.net/sfu/businessobjects _______________________________________________ Emc-users mailing list Emc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-users
