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

Showing content from https://docs.racket-lang.org/reference/Byte_and_String_Output.html below:

13.3 Byte and String Output

Writes a single character to out; more precisely, the bytes that are the UTF-8 encoding of char are written to out.

Writes a single byte to out.

Writes characters to

from

starting from index

(inclusive) up to

(exclusive). Like

, the

exception is raised if

or

is out-of-range for

.

The result is the number of characters written to out, which is always (- end-pos start-pos).

If str is mutable, mutations after write-string returns do not affect the characters written to out. (This independence from mutation is not a special property of write-string, but instead generally true of output functions.)

Like

, but returns without blocking after writing as many bytes as it can immediately flush. It blocks only if no bytes can be flushed immediately. The result is the number of bytes written and flushed to

; if

is the same as

, then the result can be

(indicating a successful flush of any buffered data), otherwise the result is between

and

, inclusive.

The write-bytes-avail procedure never drops bytes; if write-bytes-avail successfully writes some bytes and then encounters an error, it suppresses the error and returns the number of written bytes. (The error will be triggered by future writes.) If an error is encountered before any bytes have been written, an exception is raised.

Like

, but never blocks, returns

if the port contains buffered data that cannot be written immediately, and returns

if the port’s internal buffer (if any) is flushed but no additional bytes can be written immediately.

Like

, except that breaks are enabled during the write. The procedure provides a guarantee about the interaction of writing and breaks: if breaking is disabled when

is called, and if the

exception is raised as a result of the call, then no bytes will have been written to

. See also

.

Writes

directly to

if the port supports special writes, or raises

if the port does not support special write. The result is always

, indicating that the write succeeded.

Like

, but without blocking. If

cannot be written immediately, the result is

without writing

, otherwise the result is

and

is written.

Synchronizing on the object starts a write from bstr, and the event becomes ready when bytes are written (unbuffered) to the port. If start-pos and end-pos are the same, then the synchronization result is 0 when the port’s internal buffer (if any) is flushed, otherwise the result is a positive exact integer. If the event is not selected in a synchronization, then no bytes will have been written to out.

Similar to

, but instead of writing the special value immediately, it returns a synchronizable event (see

). The

must support atomic writes, as indicated by

.

Synchronizing on the object starts a write of the special value, and the event becomes ready when the value is written (unbuffered) to the port. If the event is not selected in a synchronization, then no value will have been written to out.

Returns

if procedures like

can write arbitrary values to the port. Racket’s file-stream ports, pipes, string ports, and TCP ports all reject special values, but ports created with

(see

) may support them.

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