| Summary: | We need the client API to support separate out and err streams. | ||||||
|---|---|---|---|---|---|---|---|
| Product: | z_Archived | Reporter: | Michael Spivak-Baranov <Michael.Spivak.Baranov> | ||||
| Component: | TPTP | Assignee: | Guru Nagarajan <guru.nagarajan> | ||||
| Status: | CLOSED FIXED | QA Contact: | |||||
| Severity: | enhancement | ||||||
| Priority: | P1 | CC: | igor.alelekov, karla.callaghan | ||||
| Version: | unspecified | Keywords: | plan | ||||
| Target Milestone: | --- | ||||||
| Hardware: | PC | ||||||
| OS: | All | ||||||
| Whiteboard: | closed460 | ||||||
| Attachments: |
|
||||||
|
Description
Michael Spivak-Baranov
Created attachment 55497 [details]
separation of stdout and sterr streams
Suggested patch implements separation of stdout and stderr console streams.
To activate it user should use new API call to set sepearate IDataProcessor for stterr processing: IConsole.setDataProcessor (IDataProcessor, IConsole.STDERR). Without this setting stdout and stderr streams will be mixed as before in common IDataProcessor.
I had a more symmetrical addition to the interface in mind. User should be able to specify stdout, stderr, or both. The original method, without args gets changed internal-only to call the new interface with the 'both' option, so that it continues to work the same and have the same interface. Added Igor to CC list. This enhancement is desired in 4.4. (In reply to comment #2) > I had a more symmetrical addition to the interface in mind. User should be > able to specify stdout, stderr, or both. The original method, without args > gets changed internal-only to call the new interface with the 'both' option, so > that it continues to work the same and have the same interface. Yes, this is exactly the same. With suggested changes user is able to specify stdout and sterr. With original method without stream specifying, stdout and stderr are mixed as before. Setting target to 4.4. Patch applied and verified For queries, all 4.4 items need to be P1 As of TPTP 4.6.0, TPTP is in maintenance mode and focusing on improving quality by resolving relevant enhancements/defects and increasing test coverage through test creation, automation, Build Verification Tests (BVTs), and expanded run-time execution. As part of the TPTP Bugzilla housecleaning process (see http://wiki.eclipse.org/Bugzilla_Housecleaning_Processes), this enhancement/defect is verified/closed by the Project Lead since this enhancement/defect has been resolved and unverified for more than 1 year and considered to be fixed. If this enhancement/defect is still unresolved and reproducible in the latest TPTP release (http://www.eclipse.org/tptp/home/downloads/), please re-open. |