Anonymous user
Talk:Read a configuration file: Difference between revisions
→REXX vs ooRexx: added a note about the REXX program example (and it's fix). -- ~~~~
m (→"Standard": added ubiquitous comma use. -- ~~~~) |
(→REXX vs ooRexx: added a note about the REXX program example (and it's fix). -- ~~~~) |
||
| (5 intermediate revisions by 2 users not shown) | |||
Line 25:
I have replied to the reason for two comment characters on a previous occasion: The semicolon can be removed by an automated configurator. A hash can never be removed by a configurator.
: Are we supposed to use the examples shown? Most people have "corrected" the spelling of <tt> NEEDSPEELING </tt> which means ''it needs climbing''. It's old word (1513 ce, chiefly Scottish) -- [[User:Gerard Schildberger|Gerard Schildberger]] 08:19, 29 March 2012 (UTC)
== "Standard" ==
Line 93:
[[User:Markhobley|Markhobley]] 19:11, 24 April 2011 (UTC)
== REXX vs ooRexx ==
Can you please tell us what did not work on which classic Rexx? (except, maybe, for the first line) --[[User:Walterpachl|Walterpachl]] ([[User talk:Walterpachl|talk]]) 07:10, 24 July 2013 (UTC)
: The example that was moved to ooRexx had a comment: ''This program was tested using Open Object Rexx 4.1.1.''
: The following caused problems with various Classic REXXes:
:: * The use of '''line~left(3)''' (Regina, PC/REXX, Personal REXX, R4 [et al]).
:: * Some '''stream''' options weren't recognized (et al).
:: * The first line raised a '''syntax''' error (PC/REXX, Personal REXX, R4).
:: * The '''IF arg(1) = '-h', ...''' construct of using '''then''' wasn't recognized (et al).
:: * The use of '''any''' with the '''signal''' statement (et al).
:: * Received an ''incorrect call to routine'' '''value''' ----- at this point, I stopped looking for more errors.
: I don't feel comfortable doing this level of debugging/bench-testing of a REXX program that clearly wasn't tested with any Classic REXX. Maybe the author of the program could perform that task better. -- [[User:Gerard Schildberger|Gerard Schildberger]] ([[User talk:Gerard Schildberger|talk]]) 17:31, 24 July 2013 (UTC)
::: Thank you for telling me/us (I am NOT the author). --[[User:Walterpachl|Walterpachl]] ([[User talk:Walterpachl|talk]]) 18:22, 24 July 2013 (UTC)
:::: I tested now the REXX program and I think that there is a problem with bad variable names
<lang rexx>
varList=varList xxx /*add it to the list of vARiables*/
if value='' then value='true' /*if no value, then use "true". */
if symbol(xxx)=='BAD' then do /*can REXX use the variable name?*/
Say xxx 'is a bad name'
badVar=badVar+1; bad=bad xxx; iterate
end
</lang>
:::: bad names should not go into varlist!?! --[[User:Walterpachl|Walterpachl]] ([[User talk:Walterpachl|talk]]) 19:47, 24 July 2013 (UTC)
::::: Yes, you're correct. If the variable name (in the configuration file) isn't a legal REXX variable name, then it shouldn't be added to the list of variable names (varList) in the REXX program. The REXX code has been fixed. -- [[User:Gerard Schildberger|Gerard Schildberger]] ([[User talk:Gerard Schildberger|talk]]) 18:12, 27 July 2013 (UTC)
| |||