Unit Instance

HTTP 200 OK
Allow: GET, PUT, PATCH, DELETE, HEAD, OPTIONS
Content-Type: application/json
Vary: Accept

{
    "translation": "https://translate-dev.freebsd.org/api/translations/documentation/booksdesign-44bsd_index/it_IT/?format=api",
    "source": [
        "Demands for dynamic memory allocation in the kernel have increased as more services have been added.  A generalized memory allocator reduces the complexity of writing code inside the kernel.  Thus, the 4.4BSD kernel has a single memory allocator that can be used by any part of the system.  It has an interface similar to the C library routines _malloc_ and _free_ that provide memory allocation to application programs crossref:design-44bsd[biblio-mckusick-2, [McKusick & Karels, 1988]].  Like the C library interface, the allocation routine takes a parameter specifying the size of memory that is needed.  The range of sizes for memory requests is not constrained; however, physical memory is allocated and is not paged.  The free routine takes a pointer to the storage being freed, but does not require the size of the piece of memory being freed."
    ],
    "previous_source": "",
    "target": [
        ""
    ],
    "id_hash": -4776766297336190321,
    "content_hash": -4776766297336190321,
    "location": "documentation/content/en/books/design-44bsd/_index.adoc:398",
    "context": "",
    "note": "type: Plain text",
    "flags": "",
    "labels": [],
    "state": 0,
    "fuzzy": false,
    "translated": false,
    "approved": false,
    "position": 165,
    "has_suggestion": false,
    "has_comment": false,
    "has_failing_check": false,
    "num_words": 135,
    "source_unit": "https://translate-dev.freebsd.org/api/units/1711286/?format=api",
    "priority": 100,
    "id": 1711357,
    "web_url": "https://translate-dev.freebsd.org/translate/documentation/booksdesign-44bsd_index/it_IT/?checksum=3db5845c6837ea8f",
    "url": "https://translate-dev.freebsd.org/api/units/1711357/?format=api",
    "explanation": "",
    "extra_flags": "",
    "pending": false,
    "timestamp": "2024-09-14T20:35:32.401534Z"
}