Talk:Subset sum problem: Difference between revisions

m
→‎how many solutions?: correct spelling of ''variable''. -- ~~~~
(→‎how many solutions?: added comment about the way REXX handles the resolving of subroutine invocations. -- ~~~~)
m (→‎how many solutions?: correct spelling of ''variable''. -- ~~~~)
Line 35:
:::::::: Come to think of it, did the interpreter just call the shell when it couldn't resolve "combN"? That's seriously naughty. --[[User:Ledrug|Ledrug]] 07:42, 8 May 2012 (UTC)
 
::::::::: Yes, that's the way REXX works. Any function/subroutine not in the program, REXX just looks elsewhere. Normally, it would be another REXX program in a common repository (such as a folder) for such things. There's nothing in the language to distinguish a subroutine that could be written in REXX, assembler, Java, etc. This is due to the environment that REXX was developed in, where any program can invoke another program, no matter what language it was written in (where program invocation had a common linkage). This is a mechanism to force REXX to look outside the program for subroutine execution by inclosing the subroutine name in quotes or apostrophes. As an aside, someone has written an interface for REXX to call (use) any Java subroutines (I'm not sure what Java calls such stuff). It's the writing of the linkage (interface) that's tricky. REXX has the same difficulity as PL/I does, it's variable types are, for a lack of a better word, so non-traditional that PL/I had to resort to something called "''dope vectors"'' to describe the variblevariable types. I think the closest thing I could call REXX variables would be ''non-null terminated character strings''. -- [[User:Gerard Schildberger|Gerard Schildberger]] 16:50, 8 May 2012 (UTC)