Deutsch   English   Français   Italiano  
<20250320172922.00002a08@yahoo.com>

View for Bookmarking (what is this?)
Look up another Usenet article

Path: ...!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!eternal-september.org!.POSTED!not-for-mail
From: Michael S <already5chosen@yahoo.com>
Newsgroups: comp.lang.c
Subject: Re: Suggested method for returning a string from a C program?
Date: Thu, 20 Mar 2025 17:29:22 +0200
Organization: A noiseless patient Spider
Lines: 26
Message-ID: <20250320172922.00002a08@yahoo.com>
References: <vrd77d$3nvtf$2@dont-email.me>
	<868qp1ra5f.fsf@linuxsc.com>
	<vrdhok$47cb$2@dont-email.me>
	<20250319115550.0000676f@yahoo.com>
	<vreuj1$1asii$4@dont-email.me>
	<vreve4$19klp$2@dont-email.me>
	<20250319201903.00005452@yahoo.com>
	<86r02roqdq.fsf@linuxsc.com>
	<vrh1br$35029$2@dont-email.me>
	<LRUCP.2$541.0@fx47.iad>
	<vrh71t$3be42$1@dont-email.me>
	<vrh9vh$3ev9o$1@dont-email.me>
	<20250320165914.000030eb@yahoo.com>
	<vrhbfl$3g9qg$1@dont-email.me>
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Injection-Date: Thu, 20 Mar 2025 16:29:23 +0100 (CET)
Injection-Info: dont-email.me; posting-host="06aeb3a5c52b0f3f8b2b960e1aa73887";
	logging-data="3040672"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX19hNrONcIYx3VYIoS3IBN3DE/RJ2VoShL4="
Cancel-Lock: sha1:4j9rQq0hQiHjFCbY6icZASG+WI4=
X-Newsreader: Claws Mail 3.19.1 (GTK+ 2.24.33; x86_64-w64-mingw32)
Bytes: 2230

On Thu, 20 Mar 2025 15:16:05 -0000 (UTC)
Muttley@DastardlyHQ.org wrote:

> On Thu, 20 Mar 2025 16:59:14 +0200
> Michael S <already5chosen@yahoo.com> wibbled:
> >On Thu, 20 Mar 2025 14:50:25 -0000 (UTC)
> >Muttley@DastardlyHQ.org wrote:
> >  
> >> 
> >> What makes you think they're macros?
> >>   
> >
> >PRIu64 and PRId64 are macros. They are ugly.  
> 
> Never even heard of them. Looking them up I can't see much use for
> them frankly except if you're starting out on an unknown system and
> can't find out the info any other way which would be ... odd.
> 
> 

Then how exactly do you printf value of type int64_t in a code that
expected to pass [gcc] compilation with no warnings on two platforms,
one of which is 64-bit Unix/Linux and another is just about anything
else?