Groups | Search | Server Info | Login | Register
Groups > comp.sys.apple2.programmer > #6289
| From | Peter 'Shaggy' Haywood <phaywood@alphalink.com.au> |
|---|---|
| Newsgroups | comp.sys.apple2.programmer |
| Subject | Re: malloc with cc65 |
| Date | 2023-12-27 10:00 +1100 |
| Organization | A noiseless patient Spider |
| Message-ID | <rh2s5k-642.ln1@hendrix.foo> (permalink) |
| References | (2 earlier) <20231214215955.353cd4e4@smilodon-gracilis> <ulirs5$4fr4$1@solani.org> <20231218005802.24df6e51@smilodon-gracilis> <ulq7su$3g1p$1@solani.org> <20231220105200.7f518465@smilodon-gracilis> |
Groovy hepcat Bill Chatfield was jivin' in comp.sys.apple2.programmer on
Thu, 21 Dec 2023 02:52 am. It's a cool scene! Dig it.
> On Mon, 18 Dec 2023 19:51:58 -0000 (UTC)
> Oliver Schmidt <ol.sc@web.de> wrote:
>
>> No, the syntax above isn't for assigning a value to a pointer. It's
>> for assigning a value to the address the pointer points to.
>
> OMG, it's been too long since I've written C code. Of, course you're
> right and I knew that. The overloading of the * operator in one place
> to define a pointer and in another place, the exact opposite, to
> access the data pointed to by a pointer, has always perplexed me.
There's no overloading going on here (notwithstanding its use the
multiplication operator). It's really quite simple. The * operator
means "the object pointed at". When used in a declaration it still
means "the object pointed at". A pointer to foo (where foo is a type)
declaration essentially means, "Declare an object which is a pointer
such that the object pointed at by it is a foo."
--
----- Dig the NEW and IMPROVED news sig!! -----
-------------- Shaggy was here! ---------------
Ain't I'm a dawg!!
Back to comp.sys.apple2.programmer | Previous | Next — Previous in thread | Next in thread | Find similar
malloc with cc65 Bill Chatfield <bill_chatfield@yahoo.com> - 2023-12-14 13:53 -0500
Re: malloc with cc65 Oliver Schmidt <ol.sc@web.de> - 2023-12-14 22:34 +0000
Re: malloc with cc65 Bill Chatfield <bill_chatfield@yahoo.com> - 2023-12-14 21:59 -0500
Re: malloc with cc65 Oliver Schmidt <ol.sc@web.de> - 2023-12-16 00:43 +0000
Re: malloc with cc65 Bill Chatfield <bill_chatfield@yahoo.com> - 2023-12-18 00:58 -0500
Re: malloc with cc65 Oliver Schmidt <ol.sc@web.de> - 2023-12-18 19:51 +0000
Re: malloc with cc65 Bill Chatfield <bill_chatfield@yahoo.com> - 2023-12-20 10:52 -0500
Re: malloc with cc65 Peter 'Shaggy' Haywood <phaywood@alphalink.com.au> - 2023-12-27 10:00 +1100
Re: malloc with cc65 Bill Chatfield <bill_chatfield@yahoo.com> - 2023-12-31 11:58 -0500
Re: malloc with cc65 Peter 'Shaggy' Haywood <phaywood@alphalink.com.au> - 2024-01-03 19:05 +1100
Re: malloc with cc65 Colin Leroy-Mira <colin@colino.net> - 2024-02-01 21:54 +0100
csiph-web