Menu
▾
▴
oorexx-bugs
|
From: SourceForge.net <no...@so...> - 2006-04-25 17:20:58
|
Bugs item #1476245, was opened at 2006-04-25 10:11 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=684730&aid=1476245&group_id=119701 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Interpreter Group: v3.0 Status: Open Resolution: None Priority: 5 Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: linein incorrect with '0c'x on input Initial Comment: When an input record is ended with only a '0d'x character and then followed with a '0c'x character, the '0c'x character is included in the record instead of the following record read with linein. Test case with sample data included in zip file. Using ooRexx 3.0.1 on Win2k Pro SP4. Test works on IBM ObjRexx 1.0.3.0 as expected. I may be contacted at art...@ar... - Art Heimsoth ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=684730&aid=1476245&group_id=119701 |
|
From: SourceForge.net <no...@so...> - 2006-05-22 16:31:28
|
Bugs item #1476245, was opened at 2006-04-25 13:11 Message generated for change (Settings changed) made by bigrixx You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=684730&aid=1476245&group_id=119701 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Interpreter Group: v3.0 Status: Open Resolution: None Priority: 5 Submitted By: Nobody/Anonymous (nobody) >Assigned to: Rick McGuire (bigrixx) Summary: linein incorrect with '0c'x on input Initial Comment: When an input record is ended with only a '0d'x character and then followed with a '0c'x character, the '0c'x character is included in the record instead of the following record read with linein. Test case with sample data included in zip file. Using ooRexx 3.0.1 on Win2k Pro SP4. Test works on IBM ObjRexx 1.0.3.0 as expected. I may be contacted at art...@ar... - Art Heimsoth ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=684730&aid=1476245&group_id=119701 |
|
From: SourceForge.net <no...@so...> - 2006-05-23 11:24:04
|
Bugs item #1476245, was opened at 2006-04-25 13:11 Message generated for change (Comment added) made by bigrixx You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=684730&aid=1476245&group_id=119701 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Interpreter Group: v3.0 Status: Open >Resolution: Rejected Priority: 5 Submitted By: Nobody/Anonymous (nobody) Assigned to: Rick McGuire (bigrixx) Summary: linein incorrect with '0c'x on input Initial Comment: When an input record is ended with only a '0d'x character and then followed with a '0c'x character, the '0c'x character is included in the record instead of the following record read with linein. Test case with sample data included in zip file. Using ooRexx 3.0.1 on Win2k Pro SP4. Test works on IBM ObjRexx 1.0.3.0 as expected. I may be contacted at art...@ar... - Art Heimsoth ---------------------------------------------------------------------- >Comment By: Rick McGuire (bigrixx) Date: 2006-05-23 07:24 Message: Logged In: YES user_id=1125291 IBM ObjRexx 1.0.3.0 is the one that has the bug, which was fixed by the IBM 2.1.3 version. The character '0d'x is NOT a valid end-of-line indicators. The only valid lineend markers are '0a'x and '0d0a'x. Technically, only the '0a'x indicates the presense of a new line, but if the '0a'x is preceeded by '0d'x, then that character is also removed. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=684730&aid=1476245&group_id=119701 |
|
From: SourceForge.net <no...@so...> - 2006-05-25 17:31:57
|
Bugs item #1476245, was opened at 2006-04-25 13:11 Message generated for change (Settings changed) made by bigrixx You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=684730&aid=1476245&group_id=119701 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Interpreter Group: v3.0 >Status: Closed Resolution: Rejected Priority: 5 Submitted By: Nobody/Anonymous (nobody) Assigned to: Rick McGuire (bigrixx) Summary: linein incorrect with '0c'x on input Initial Comment: When an input record is ended with only a '0d'x character and then followed with a '0c'x character, the '0c'x character is included in the record instead of the following record read with linein. Test case with sample data included in zip file. Using ooRexx 3.0.1 on Win2k Pro SP4. Test works on IBM ObjRexx 1.0.3.0 as expected. I may be contacted at art...@ar... - Art Heimsoth ---------------------------------------------------------------------- Comment By: Rick McGuire (bigrixx) Date: 2006-05-23 07:24 Message: Logged In: YES user_id=1125291 IBM ObjRexx 1.0.3.0 is the one that has the bug, which was fixed by the IBM 2.1.3 version. The character '0d'x is NOT a valid end-of-line indicators. The only valid lineend markers are '0a'x and '0d0a'x. Technically, only the '0a'x indicates the presense of a new line, but if the '0a'x is preceeded by '0d'x, then that character is also removed. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=684730&aid=1476245&group_id=119701 |
Thanks for helping keep SourceForge clean.
X