#42 closed defect (fixed)
Unaligned indention with REXX
| Reported by: | jep | Owned by: | Gregg Young |
|---|---|---|---|
| Priority: | minor | Milestone: | Release_1.0 |
| Component: | eFTE core | Version: | PreRelease_1.0 |
| Keywords: | Cc: |
Description
The problem found in earlier OS/2 versions of FTE is also present in eFTE/2. The Windows/DOS¹ version indent DO ... END and nested IF ... THEN ELSE as expected.
/* Example of some basic code in REXX */
IF ARG(1) = THEN
DO
input = 'NONE'
END /* <- Not ok */
IF ARG(1) = THEN
DO
input = 'NONE'
END /* <- OK! */
¹) Indention is ok in
About: fte 0.49.13 Copyright (c) 1994-1998 Marko Macek Copyright (c) 2000-2001 Others
Change History (4)
comment:1 by , 9 years ago
| Owner: | set to |
|---|---|
| Status: | new → accepted |
Version 0, edited 9 years ago by (next)
comment:3 by , 9 years ago
| Milestone: | → Release_1.0 |
|---|
comment:4 by , 9 years ago
| Version: | → PreRelease_1.0 |
|---|
Note:
See TracTickets
for help on using tickets.
I did some research on this and found that the placement of catch finally and end were all the same relative to do loop and select. The code in eFTE/2 set catch and end differently and ignored finally. I also found that 2 different indent style were used. One indented the end relative to the do the other aligned them. I am not a really a REXX user so I have no opinion as to which is more correct so I have add a variable REXX_End_Offset which allows the user to decide.However I have done it in a way that always aligns catch and finally with end since that was consistent in all the examples I reviewed.