Path: csiph.com!eternal-september.org!feeder.eternal-september.org!mx02.eternal-september.org!.POSTED!not-for-mail From: Keith Thompson Newsgroups: comp.lang.c Subject: Re: double strtod( const char *nPtr, char **endPrt); Date: Thu, 12 Nov 2015 18:07:13 -0800 Organization: None to speak of Lines: 29 Message-ID: References: <6b8eee47-6184-45f2-8b56-b0e51c16a763@googlegroups.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Injection-Info: mx02.eternal-september.org; posting-host="945944de09706c9b4e29b53c9d2efdc2"; logging-data="15847"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1/P12xzrY5hP/EeGxfjZDTQ" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.1 (gnu/linux) Cancel-Lock: sha1:od7s9NDC2i6cJ6O0O5a0J0OYyrw= sha1:PEv4DBGXq0xJgsNFpeptSJ23b64= Xref: csiph.com comp.lang.c:75911 Eric Sosman writes: > On 11/12/2015 6:15 PM, glen herrmannsfeldt wrote: >> Keith Thompson wrote: >>> supercat@casperkitty.com writes: >> (snip) >>>> While I don't think anything would forbid an implementation where string >>>> literals could create objects at run time, I would suggest that they more >>>> often create objects at compile time which are aggregated into an object >>>> which gets created at load time. String literal expressions then identify >>>> pieces of that object. >> >>> Objects don't exist at compile time. >> >> I suspect it isn't part of the C standard, but most systems create >> static objects at compile time. They exist in the object module, >> and resultant load module. > > I think Keith's point is that the contents of the "object module" > and "load module" are not objects until run time; they're just > instructions to the starter-upper to create some objects before > calling main(). Exactly. -- Keith Thompson (The_Other_Keith) kst-u@mib.org Working, but not speaking, for JetHead Development, Inc. "We must do something. This is something. Therefore, we must do this." -- Antony Jay and Jonathan Lynn, "Yes Minister"