Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from http://docs.racket-lang.org/reference/port-lib.html below:

13.1.10 More Port Constructors, Procedures, and Events

Returns a list whose elements are produced by calling

on

until it produces

.

Examples:

Reads all characters from in and returns them as a string. The input port is closed unless close? is #f.

Example:

Changed in version 6.8.0.2 of package base: Added the #:close? argument.

Reads all bytes from

and returns them as a

. The input port is closed unless

is

.

Example:

Changed in version 6.8.0.2 of package base: Added the #:close? argument.

Read all characters from

, breaking them into lines. The

argument is the same as the second argument to

, but the default is

instead of

. The input port is closed unless

is

.

Example:

'("line 1" "line 2" "  line 3" "line 4")

Changed in version 6.8.0.2 of package base: Added the #:close? argument.

Like

, but reading bytes and collecting them into lines like

. The input port is closed unless

is

.

Example:

'(#"line 1" #"line 2" #"  line 3" #"line 4")

Changed in version 6.8.0.2 of package base: Added the #:close? argument.

Uses

on each element of

to

, adding

after each element.

Calls proc with an output port that accumulates all output into a string, and returns the string.

The port passed to proc is like the one created by open-output-string, except that it is wrapped via dup-output-port, so that proc cannot access the port’s content using get-output-string. If control jumps back into proc, the port continues to accumulate new data, and call-with-output-string returns both the old data and newly accumulated data.

Like

, but returns the accumulated result in a

instead of a string. Furthermore, the port’s content is emptied when

returns, so that if control jumps back into

and returns a second time, only the newly accumulated bytes are returned.

Equivalent to

Equivalent to

Equivalent to

Equivalent to

Takes any number of input ports and returns an input port. Reading from the input port draws bytes (and special non-byte values) from the given input ports in order. If close-at-eof? is true, then each port is closed when an end-of-file is encountered from the port, or when the result input port is closed. Otherwise, data not read from the returned input port remains available for reading in its original input port.

The name argument determines the name as reported by object-name for the returned input port.

See also merge-input, which interleaves data from multiple input ports as it becomes available.

Changed in version 6.90.0.19 of package base: Added the name argument.

Similar to

, but if the given

returns an event, the event’s value must be

. The resulting port’s peek operation is implemented automatically (in terms of

) in a way that can handle special non-byte values. The progress-event and commit operations are also implemented automatically. The resulting port is thread-safe, but not kill-safe (i.e., if a thread is terminated or suspended while using the port, the port may become damaged).

The read-in, close, get-location, count-lines!, init-position, and buffer-mode procedures are the same as for make-input-port.

The fast-peek argument can be either #f or a procedure of three arguments: a byte string to receive a peek, a skip count, and a procedure of two arguments. The fast-peek procedure can either implement the requested peek, or it can dispatch to its third argument to implement the peek. The fast-peek is not used when a peek request has an associated progress event.

The buffering? argument determines whether read-in can be called to read more characters than are immediately demanded by the user of the new port. If buffer-mode is not #f, then buffering? determines the initial buffer mode, and buffering? is enabled after a buffering change only if the new mode is 'block.

If on-consumed is not #f, it is called when data is read (or committed) from the port, as opposed to merely peeked. The argument to on-consumed is the result value of the port’s reading procedure, so it can be an integer or any result from read-in.

Returns a port whose content is drawn from in, but where an end-of-file is reported after limit bytes (and non-byte special values) have been read. If close-orig? is true, then the original port is closed if the returned port is closed.

Bytes are consumed from in only when they are consumed from the returned port. In particular, peeking into the returned port peeks into the original port.

If in is used directly while the resulting port is also used, then the limit bytes provided by the port need not be contiguous parts of the original port’s stream.

Returns two ports: an input port and an output port. The ports behave like those returned by

, except that the ports support non-byte values written with procedures such as

and read with procedures such as

.

The limit argument determines the maximum capacity of the pipe in bytes, but this limit is disabled if special values are written to the pipe before limit is reached. The limit is re-enabled after the special value is read from the pipe.

The optional in-name and out-name arguments determine the names of the result ports.

Accepts two output ports and returns a new output port combining the original ports. When written to, the combined port first writes as many bytes as possible to a-out, and then tries to write the same number of bytes to b-out. If that doesn’t succeed, what is left over is buffered and no further writes can go through until the ports are evened out. The port is ready (for the purposes of synchronization) when each port reports being ready. However, the first port may stop being ready while waiting on the second port to sync, so it cannot be guaranteed that both ports are ready at once. Closing the combined port is done after writing all remaining bytes to b-out.

Added in version 7.7.0.10 of package base.

Accepts two input ports and returns a new input port. The new port merges the data from two original ports, so data can be read from the new port whenever it is available from either of the two original ports. The data from the original ports are interleaved. When an end-of-file has been read from an original port, it no longer contributes characters to the new port. After an end-of-file has been read from both original ports, the new port returns end-of-file. Closing the merged port does not close the original ports.

The optional buffer-limit argument limits the number of bytes to be buffered from a-in and b-in, so that the merge process does not advance arbitrarily beyond the rate of consumption of the merged data. A #f value disables the limit. As for make-pipe-with-specials, buffer-limit does not apply when a special value is produced by one of the input ports before the limit is reached.

See also input-port-append, which concatenates input streams instead of interleaving them.

Creates and returns an output port that discards all output sent to it (without blocking). The

argument is used as the port’s name. If the

argument is true, then the resulting port supports

, otherwise it does not.

Creates and returns an input port that always returns

(without blocking). The

argument is used as the port’s name.

Added in version 8.15.0.2 of package base.

Returns an input port whose content is determined by peeking into in. In other words, the resulting port contains an internal skip count, and each read of the port peeks into in with the internal skip count, and then increments the skip count according to the amount of data successfully peeked.

The optional name argument is the name of the resulting port. The skip argument is the port initial skip count, and it defaults to 0.

The resulting port’s initial position (as reported by file-position) is (- init-position 1), no matter the position of in.

The resulting port supports buffering, and a 'block buffer mode allows the port to peek further into in than requested. The resulting port’s initial buffer mode is 'block, unless in supports buffer mode and its mode is initially 'none (i.e., the initial buffer mode is taken from in when it supports buffering). If in supports buffering, adjusting the resulting port’s buffer mode via file-stream-buffer-mode adjusts in’s buffer mode.

For example, when you read from a peeking port, you see the same answers as when you read from the original port:

Examples:

Beware that the read from the original port is invisible to the peeking port, which keeps its own separate internal counter, and thus interleaving reads on the two ports can produce confusing results. Continuing the example before, if we read three more characters from the peeking port, we end up skipping over the 456 in the port (but only because we disabled buffering above):

Example:

If we had left the buffer mode of a-peeking-port alone, that last read-string would have likely produced "456" as a result of buffering bytes from an-original-port earlier.

Changed in version 6.1.0.3 of package base: Enabled buffering and buffer-mode adjustments via file-stream-buffer-mode, and set the port’s initial buffer mode to that of in.

Produces an input port that draws bytes from

, but converts the byte stream using

. In addition, if

is true, then decoded sequences that correspond to UTF-8 encodings of

,

,

,

, and

are all converted to the UTF-8 encoding of

.

If error-bytes is provided and not #f, then the given byte sequence is used in place of bytes from in that trigger conversion errors. Otherwise, if a conversion is encountered, enc-error is called, which must raise an exception.

If close? is true, then closing the result input port also closes in. The name argument is used as the name of the result input port.

In non-buffered mode, the resulting input port attempts to draw bytes from in only as needed to satisfy requests. Toward that end, the input port assumes that at least n bytes must be read to satisfy a request for n bytes. (This is true even if the port has already drawn some bytes, as long as those bytes form an incomplete encoding sequence.)

Produces an output port that directs bytes to

, but converts its byte stream using

. In addition, if

is not

, then bytes written to the port that are the UTF-8 encoding of

are first converted to

(before applying the convert from UTF-8 to

).

If error-bytes is provided and not #f, then the given byte sequence is used in place of bytes that have been sent to the output port and that trigger conversion errors. Otherwise, enc-error is called, which must raise an exception.

If close? is true, then closing the result output port also closes out. The name argument is used as the name of the result output port.

The resulting port supports buffering, and the initial buffer mode is (or (file-stream-buffer-mode out) 'block). In 'block mode, the port’s buffer is flushed only when it is full or a flush is requested explicitly. In 'line mode, the buffer is flushed whenever a newline or carriage-return byte is written to the port. In 'none mode, the port’s buffer is flushed after every write. Implicit flushes for 'line or 'none leave bytes in the buffer when they are part of an incomplete encoding sequence.

The resulting output port does not support atomic writes. An explicit flush or special-write to the output port can hang if the most recently written bytes form an incomplete encoding sequence.

When the port is buffered, a flush callback is registered with the current plumber to flush the buffer.

Returns an input port that draws directly from in. Closing the resulting port closes in only if close? is #t.

The new port is initialized with the port read handler of in, but setting the handler on the result port does not affect reading directly from in.

Returns an output port that propagates data directly to out. Closing the resulting port closes out only if close? is #t.

The new port is initialized with the port display handler and port write handler of out, but setting the handlers on the result port does not affect writing directly to out.

Produces an input port that is equivalent to in except in how it reports location information (and possibly its name). The resulting port’s content starts with the remaining content of in, and it starts at the given line, column, and position. A #f for the line or column means that the line and column will always be reported as #f.

The line and column values are used only if line counting is enabled for in and for the resulting port, typically through port-count-lines!. The column value determines the column for the first line (i.e., the one numbered line), and later lines start at column 0. The given position is used even if line counting is not enabled.

When line counting is on for the resulting port, reading from in instead of the resulting port increments location reports from the resulting port. Otherwise, the resulting port’s position does not increment when data is read from in.

If close? is true, then closing the resulting port also closes in. If close? is #f, then closing the resulting port does not close in.

The name argument is used as the name for the resulting port; the default value keeps the same name as in.

Like

, except that arbitrary position information can be produced (when line counting is enabled) via

, which is used as for

. If

is

, then the port counts lines in the usual way starting from

, independent of locations reported by

.

If count-lines! is supplied, it is called when line counting is enabled for the resulting port. The default is void.

Creates a port that draws from

, but each result from the port’s read and peek procedures (in the sense of

) is filtered by

and

. The filtering procedures each receive both the arguments and results of the read and peek procedures on

for each call.

If close? is true, then closing the resulting port also closes in.

Produces an input port that is equivalent to

, except that when

produces a procedure to access a special value,

is applied to the procedure to allow the special value to be replaced with an alternative. The

is called with the special-value procedure and the byte string that was given to the port’s read or peek function (see

), and the result is used as the read or peek function’s result. The

can modify the byte string to substitute a byte for the special value, but the byte string is guaranteed only to hold at least one byte.

If close? is true, then closing the resulting input port also closes in.

Returns a

that is ready when

produces an

. If

produces a mid-stream

, the

is consumed by the event only if the event is chosen in a synchronization.

If attempting to read from in raises an exception during a synchronization attempt, then the exception may be reported during the synchronization attempt, but it will silently discarded if some another event in the same synchronization is selected or if some other event raises an exception first.

Changed in version 7.5.0.3 of package base: Changed handling of read errors so they are propagated to a synchronization attempt, instead of treated as unhandled errors in a background thread.

Returns a

that is ready when

bytes can be read from

, or when an end-of-file is encountered in

. If

is

, then the event is ready immediately with

. For non-zero

, if no bytes are available before an end-of-file, the event’s result is

. Otherwise, the event’s result is a byte string of up to

bytes, which contains as many bytes as are available (up to

) before an available end-of-file. (The result is a byte string of less than

bytes only when an end-of-file is encountered.)

Bytes are read from the port if and only if the event is chosen in a synchronization, and the returned bytes always represent contiguous bytes in the port’s stream.

The event can be synchronized multiple times—even concurrently—and each synchronization corresponds to a distinct read request.

The in must support progress events, and it must not produce a special non-byte value during the read attempt.

Exceptions attempting to read from in are handled in the same way as by eof-evt.

Like

, except that the read bytes are placed into

, and the number of bytes to read corresponds to

. The event’s result is either

or the number of read bytes.

The bstr may be mutated any time after the first synchronization attempt on the event and until either the event is selected, a non-#f progress-evt is ready, or the current custodian (at the time of synchronization) is shut down. Note that there is no time bound otherwise on when bstr might be mutated if the event is not selected by a synchronzation; nevertheless, multiple synchronization attempts can use the same result from read-bytes!-evt as long as there is no intervening read on in until one of the synchronization attempts selects the event.

Exceptions attempting to read from in are handled in the same way as by eof-evt.

Like

, except that the event reads only as many bytes as are immediately available, after at least one byte or one

becomes available.

Like

, but for character strings instead of byte strings.

Like

, but for a character string instead of a byte string.

Returns a

that is ready when a line of characters or end-of-file can be read from

. The meaning of

is the same as for

. The event result is the read line of characters (not including the line separator).

A line is read from the port if and only if the event is chosen in a synchronization, and the returned line always represents contiguous bytes in the port’s stream.

Exceptions attempting to read from in are handled in the same way as by eof-evt.

Like

, but returns a byte string instead of a string.

Like the

, etc., functions, but for peeking. The

argument indicates the number of bytes to skip, and

indicates an event that effectively cancels the peek (so that the event never becomes ready). The

argument can be

, in which case the event is never canceled.

Returns a

that is ready when

matches the stream of bytes/characters from

; see also

. The event’s value is the result of the match, in the same form as the result of

.

If pattern does not require a start-of-stream match, then bytes skipped to complete the match are read and discarded when the event is chosen in a synchronization.

Bytes are read from the port if and only if the event is chosen in a synchronization, and the returned match always represents contiguous bytes in the port’s stream. If not-yet-available bytes from the port might contribute to the match, the event is not ready. Similarly, if pattern begins with a start-of-stream ^ and the pattern does not initially match, then the event cannot become ready until bytes have been read from the port.

The event can be synchronized multiple times—even concurrently—and each synchronization corresponds to a distinct match request.

The in port must support progress events. If in returns a special non-byte value during the match attempt, it is treated like eof.

Exceptions attempting to read from in are handled in the same way as by eof-evt.

Reads data from

, converts it using

and writes the converted bytes to

. The

procedure returns after reaching

in

.

If opening the converter fails, the exn:fail exception is raised. Similarly, if a conversion error occurs at any point while reading from in, then exn:fail exception is raised.

Reads data from

and writes it back out to

, returning when

produces

. The copy is efficient, and it is without significant buffer delays (i.e., a byte that becomes available on

is immediately transferred to

, even if future reads on

must block). If

produces a special non-byte value, it is transferred to

using

.

This function is often called from a “background” thread to continuously pump data from one stream to another.

If multiple outs are provided, data from in is written to every out. The different outs block output to each other, because each block of data read from in is written completely to one out before moving to the next out. The outs are written in the provided order, so non-blocking ports (e.g., file output ports) should be placed first in the argument list.

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4