Path: csiph.com!news.swapon.de!eternal-september.org!feeder.eternal-september.org!reader01.eternal-september.org!.POSTED!not-for-mail From: Keith Thompson Newsgroups: comp.lang.c Subject: Re: memcpy not memcpying? Date: Fri, 01 Nov 2019 10:22:56 -0700 Organization: None to speak of Lines: 21 Message-ID: References: <2LVuF.7$BF1.0@fx26.iad> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Injection-Info: reader02.eternal-september.org; posting-host="bd2070be1949be0113457798c3cfb24b"; logging-data="1127"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1+Z5sAvjPOa7iaVwDeMLz+b" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.1 (gnu/linux) Cancel-Lock: sha1:MDfH9Ho9jR0KVahVmOtKweojQYI= sha1:fbK/n+8OTio4o76KJfiaAKKb3lU= Xref: csiph.com comp.lang.c:147474 Autist writes: [...] > Better use a superior language: > > #include > #include [...] This is comp.lang.c. If you want to discuss C++, there's comp.lang.c++ -- where they're no more likely to tolerate your unexplained removal of attribution lines than we are. Speaking of which -- *PLONK*. (If you're not familiar with the term, that means I'm adding you to my killfile.) -- Keith Thompson (The_Other_Keith) kst-u@mib.org Working, but not speaking, for Philips Healthcare void Void(void) { Void(); } /* The recursive call of the void */