Code

Programming Languages: C, Rexx

License: GNU Library or Lesser General Public License version 2.0 (LGPLv2)

Repositories

browse code, statistics, last commit on 2012-01-04 svn co https://regina-rexx.svn.sourceforge.net/svnroot/regina-rexx regina-rexx

Show:

What's happening?

  • Comment: all Regina versions (3.3, 3.4, 3.5 3.6)

    The two REXX programs' first comment \*prognn*/ ----- the first character should be a forward slash (/), I don't know how they got changed into a backslash. The error still persists. _____________________________ Gerard Schildberger.

    2012-05-27 21:48:06 PDT by gerardschi

  • all Regina versions (3.3, 3.4, 3.5 3.6)

    Regina REXX isn't processing DO loops with a non-non-negative increment (BY). Here's an example: 111111111111111111111111111111111 \*PROG11*/ do j=10 by -1 to 2 say j end 111111111111111111111111111111111 output is (as expected): 10 9 8 7 6 5 4 3 2 Now, example 2: 222222222222222222222222222222222 \*PROG22*/ do j=10 by 0 to 2 say j...

    2012-05-25 19:36:03 PDT by nobody

  • Rel 3.4, 3.5, and 3.6 either is wrong or Regina is

    The documentation says the option no_Single_line_comments will cause Regina to not use single line comments. It doesn't. However, the option noSingle_line_comments does work. Since it's part of the documentation (even if it's corrected), I suggest that Regina accept both forms. All other options (that allow it) just add a "no" to an option...

    2012-05-08 15:21:01 PDT by gerardschi

  • missing piece of documentation

    For the LOWER and UPPER bif, the default value for "start" isn't defined. ________________________________ Gerard Schildberger.

    2012-05-01 04:10:17 PDT by gerardschi

  • Regina is issuing misleading error message

    (For all Reginas up to and including 3.6): In the one-liner REXX program: /**/ say 'have found a \ and a : on same line!' copies(~,55) Regina is issuing the error messages: Error 35 running "D:\wrong.rex", line 1: Invalid expression Error 35.1: Invalid expression detected at "\" This is a very misleading error message ---of course, in this context, it's...

    2012-04-29 13:41:58 PDT by nobody

  • source code mismatch

    what is the reason of the source code mismatch i lexxsrc.c VS. Lexxsrc.l ? for example lexxsrc.c has case '-': /* line "--" comments */ if ( line[pos + 1] == '-' && get_options_flag( parser_data.TSD->currlevel, EXT_SINGLE_LINE_COMMENTS ) && !get_options_flag(...

    2012-04-21 04:45:58 PDT by es003481

  • Comment: Evaluation of logical expressions

    Ignore that (last) extraneous "but" to my last post. I don't know how that got there. Mea culpa. _______________________________ Gerard Schildberger.

    2012-04-16 08:54:21 PDT by gerardschi

  • Comment: Evaluation of logical expressions

    I don't know if the Rexx language standard specifies this (lack of) short-circuiting or not. I assume not, similar to how classic Pascal avoids it. A simple workaround could perhaps be "if a() then if b() then ...".

    2012-04-15 22:03:26 PDT by rugxulo

  • Parameters not recognized (Win7/64)

    I have set up the assoc, ftype, and path variables in the system. When I enter "namefix whatever" the procedure just ends. I added "Trace?I" and found that "Parse Arg options" results in "options" having a null value. I have used Regina on various flavors of Windows where this works, but I cannot find what I might be doing wrong on my Widows 7 Home...

    2012-04-15 09:04:25 PDT by mainframe73

  • Comment: Evaluation of logical expressions

    The bypassing of evaluation of expressions (when not needed to determine the result of the IF/WHEN/other statements) is called short circuits (or short circuiting). Of what I've read, the decision was made long long ago to not do short circuits/short circuiting. To illustrate a point: if func(a) & funky(b) then call thatThing; where func(a) evaluates to say...

    2012-04-12 23:57:36 PDT by gerardschi

Our Numbers