Path: ...!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!bluemanedhawk.eternal-september.org!.POSTED!not-for-mail
From: BlueManedHawk <bluemanedhawk@invalid.invalid>
Newsgroups: comp.lang.c
Subject: Re: Something like string-streams existing in "C"?
Date: Thu, 19 Dec 2024 08:32:27 -0500
Organization: A noiseless patient Spider
Lines: 8
Message-ID: <vk179b$2s9oa$1@bluemanedhawk.eternal-september.org>
References: <vjvsvb$2i07u$1@dont-email.me>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Injection-Date: Thu, 19 Dec 2024 14:32:27 +0100 (CET)
Injection-Info: bluemanedhawk.eternal-september.org; posting-host="fe570363173881e2af166cbe38ca68a8";
	logging-data="3024650"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX19mTqvR9kHNVQyHsu3GKu9dM26T8TEzAvc="
User-Agent: Betterbird (Linux)
Cancel-Lock: sha1:r3K2LpWXRD0+zKkoesuHq0vBILQ=
In-Reply-To: <vjvsvb$2i07u$1@dont-email.me>
Content-Language: en-US
Bytes: 1648

The ‘asprintf’ subroutine is standardized by POSIX.1-2024, meaning that 
you can use it now and blame somebody else if it doesn't work.  If you 
can't target POSIX, the subroutine is also _theoretically_ available 
through the feature-test macro ‘__STDC_WANT_LIB_EXT2__’, assuming that 
‘__STDC_ALLOC_LIB__’ is a predefined macro, but gLibC does not pay 
attention to that for this subroutine, and which feature-test macro does 
induce its declaration is seemingly undocumented, though it is at least 
defined through ‘_DEFAULT_SOURCE’.