taskText Extractor TXR - Tasks: task #11433, Implement a way for multiple...

 
 

You are not allowed to post comments on this tracker with your current authentication level.

task #11433: Implement a way for multiple output blocks to go to the same stream.

Submitter:  Kaz Kylheku <kkylheku>
Submitted:  Thu 13 Oct 2011 12:36:07 AM UTC
   
 
Should Start On:  Wed 12 Oct 2011 07:00:00 AM UTC Should be Finished on:  Wed 12 Oct 2011 07:00:00 AM UTC
Category:  None Priority:  5 - Normal
Status:  Done Privacy:  Public
Assigned to:  kkylheku Percent Complete:  100%
Open/Closed:  Closed Effort:  1.00

Sat 12 Oct 2013 04:20:59 AM UTC, comment #1: 

This is now implemented via the :named, :continue and :finish keywords supported in @(output), and the helper directive @(close).

Kaz Kylheku <kkylheku>
Group administrator
Thu 13 Oct 2011 12:36:07 AM UTC, original submission:  

A TXR query should be able to output data to a stream, then finish the output block and later append more data to the same stream. If the stream is a pipe, the output goes to the same pipe, not to a new instance of the pipe.

The proposal is to allow an output directive to specify (via a keyword) that the open block is connected to a named stream. Another output can specify that it goes to the same stream.

A named stream is not automatically closed at the end of the output block.

A @(close) directive could be provided to explicitly close a named stream. Perhaps an @(open) directive could be provided also.

These names can follow the scope rules common to variable bindings. Possibly, they can be in the same namespace.

Example syntax:

  @(output `!tee foo.txt` :named tee)
  Hello,
  @(end)
  @(output :into tee)
  World!
  @(end)
  @(close tee)

Kaz Kylheku <kkylheku>
Group administrator

 

(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

No files currently attached

 

Depends on the following items: None found

Items that depend on this one: None found

 

Carbon-Copy List
  • -email is unavailable- added by kkylheku (Submitted the item)
  •  

    There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.

     

    Follow 5 latest changes.

    Date Changed by Updated Field Previous Value => Replaced by
    2013-10-12 kkylheku Open/ClosedOpen Closed
    2013-10-12 kkylheku StatusNone Done
        Percent Complete0% 100%
        Assigned toNone kkylheku
        Effort16.00 1

    Back to the top

    Powered by Savane 3.13-d3ae.
    Corresponding source code