Searched refs:CharBuffer (Results 1 – 4 of 4) sorted by relevance
265 typedef struct CharBuffer { struct271 } CharBuffer; argument277 CharBuffer* cbuf = cs->opaque; in charbuffer_close()296 CharBuffer* cbuf = cs->opaque; in charbuffer_write()346 charbuffer_poll( CharBuffer* cbuf ) in charbuffer_poll()389 CharBuffer* cbuf = cs->opaque; in charbuffer_update_handlers()400 charbuffer_init( CharBuffer* cbuf, CharDriverState* endpoint ) in charbuffer_init()418 static CharBuffer _s_charbuffers[ MAX_CHAR_BUFFERS ];423 CharBuffer* cbuf = _s_charbuffers; in qemu_chr_open_buffer()424 CharBuffer* cbuf_end = cbuf + MAX_CHAR_BUFFERS; in qemu_chr_open_buffer()[all …]
50 typedef Vector<char, 512> CharBuffer; typedef215 static void encodeRelativeString(const String& rel, const TextEncoding&, CharBuffer& ouput);246 static void appendASCII(const String& base, const char* rel, size_t len, CharBuffer& buffer) in appendASCII()351 CharBuffer strBuffer; in init()401 CharBuffer parseBuffer; in init()461 CharBuffer baseStringBuffer(baseLength); in init()844 CharBuffer buffer; in decodeURLEscapeSequences()1001 CharBuffer buffer(string.length() + 1); in parse()1263 CharBuffer pathBuffer(pathEnd - pathStart + 1); in parse()1343 CharBuffer buffer(asUTF8.length() * 3 + 1); in encodeWithURLEscapeSequences()[all …]
152 III. CharBuffer objects:155 The Android emulator provides an object called a CharBuffer which acts as164 iteration, the CharBuffer will try to send data to the endpoint until it168 their own emit buffer. Note that writing to a CharBuffer always succeeds.170 Note also that calling qemu_chr_add_handler() on the CharBuffer will do the
49916 (WebCore::encodeRelativeString): Changed to put result into a CharBuffer.