Path: csiph.com!eternal-september.org!feeder.eternal-september.org!reader01.eternal-september.org!.POSTED!not-for-mail From: Keith Thompson Newsgroups: comp.lang.c++ Subject: Re: Question on a C++ string Date: Sun, 29 Dec 2019 01:45:51 -0800 Organization: None to speak of Lines: 17 Message-ID: <87fth3qxbk.fsf@nosuchdomain.example.com> References: Mime-Version: 1.0 Content-Type: text/plain Injection-Info: reader02.eternal-september.org; posting-host="e3b117bf55650e4ec854fd7e333c3408"; logging-data="4841"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX19HMKkWepaAwvf7eK+tnINu" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/26.3 (gnu/linux) Cancel-Lock: sha1:htU1usnXfMSVIgN+5bZG8sM3Vtk= sha1:RW5nsPjC+z35I94zvUxlyQxJExo= Xref: csiph.com comp.lang.c++:70760 Jorgen Grahn writes: [...] > From a C perspective, a string is a pointer to the first char in a > sequence, and the string ends with a char 0 marker. That's probably > the one your Windows API wants, if it's a C API like someone wrote. No, from a C perspective "A string is a contiguous sequence of characters terminated by and including the first null character." What you're describing is a pointer to a string (which is what is typically passed to functions). -- Keith Thompson (The_Other_Keith) Keith.S.Thompson+u@gmail.com [Note updated email address] Working, but not speaking, for Philips Healthcare void Void(void) { Void(); } /* The recursive call of the void */