fmem

KO | EN

gitlite — search

#python #react #ai #golang #go #android #rust #macos #java #awesome #cli #kubernetes #pytorch #ios

(★ 86)

A cross-platform library for opening memory-backed libc streams.

File Explorer

Download Latest Version (.zip)

- FindCriterion.cmake
- fmem.h.in
- alloc.c
- alloc.h
- fmem-fopencookie.c
- fmem-funopen.c
- fmem-open_memstream.c
- fmem-tmpfile.c
- fmem-winapi-tmpfile.c
- CMakeLists.txt
- tests.c
.appveyor.yml
.travis.yml
CMakeLists.txt
LICENSE
README.md

// repository documentation

Was this content helpful?

★ 0 (0 ratings)

# fmem

[![Unix Build Status](https://img.shields.io/travis/Snaipe/fmem/master.svg?label=linux)](https://travis-ci.org/Snaipe/fmem) 
[![Windows Build Status](https://img.shields.io/appveyor/ci/Snaipe/fmem/master.svg?label=windows)](https://ci.appveyor.com/project/Snaipe/fmem/branch/master)

A cross-platform library for opening memory-backed libc streams.

This library was written for [Criterion][criterion] to implement stringification functions for user-defined types.

## Rationale

C doesn't define any way to open "virtual" streams that write to memory rather than a real file. A lot of libc implementations roll their own nonstandard mechanisms to achieve this, namely `open_memstream`, or `fmemopen`. Other implementations provide more generic functions to call users functions for various operations on the file, like `funopen` or `fopencookie`. Finally, some implementations support none of these nonstandard functions.

fmem tries in sequence the following implementations:

* `open_memstream`.
* `fopencookie`, with growing dynamic buffer.
* `funopen`, with growing dynamic buffer.
* WinAPI temporary memory-backed file.

When no other mean is available, fmem falls back to `tmpfile()`.

[criterion]: https://github.com/Snaipe/Criterion

fmem

File Explorer

Today's picks

Was this content helpful?

Recent Feedback

fmem

File Explorer

Today's picks

Was this content helpful?

Recent Feedback

Download README