#17 Call function() syntax

closed
nobody
None
5
2007-01-03
2003-12-31
Alan Insley
No

/* valid in 3.0 not 3.3 */
call abc()
call abc(1, 2)

/* valid in 3.3 not 3.0 */
call abc(1 2)
call abc(1) (2), (3)
call abc(1) (2) (3)

/* valid */
call abc (1 2)
call abc (1) (2), (3)
call abc (1) (2) (3)

/* not valid */
call abc ()
call abc (1, 2)
call abc() 3
call abc(1, 2) (3)
call abc (1, 2) (3)

I would like a switch for the two formats that were valid
in 3.0
I also think that it would be a good idea in general.

Best Regards!
Alan

Discussion

  • Logged In: YES
    user_id=262734

    Regina will parse the environment variable
    REGINA_OPTIONS on first use of the interpreter
    in each thread. It may contain every allowed
    OPTIONS string and overwrites the default
    startup value, especially the new one
    CALLS_AS_FUNCS. This option cannot be set
    in the script itself because the parsing step
    needs the information about this hack.

    Thus, setting
    REGINA_OPTIONS=CALLS_AS_FUNCS
    will enable a compatibility mode which allows an
    extra outer parentheses pair.

    We'll have then:

    Always allowed:
    call abc(1 2)
    call abc(1) (2), (3)
    call abc(1) (2) (3)
    call abc (1 2)
    call abc (1) (2), (3)
    call abc (1) (2) (3)

    Allowed in compatibility mode but not in ANSI mode:
    call abc()
    call abc(1, 2)
    call abc ()
    call abc (1, 2)

    Never allowed:
    call abc() 3
    call abc(1, 2) (3)
    call abc (1, 2) (3)

     
  • Mark Hessling
    Mark Hessling
    2004-04-07

    • status: open --> pending
     
    • status: pending --> closed
     
  • Logged In: YES
    user_id=1312539
    Originator: NO

    This Tracker item was closed automatically by the system. It was
    previously set to a Pending status, and the original submitter
    did not respond within 1000 days (the time period specified by
    the administrator of this Tracker).