Path: csiph.com!v102.xanadu-bbs.net!xanadu-bbs.net!feeder.erje.net!eu.feeder.erje.net!eternal-september.org!feeder.eternal-september.org!news.eternal-september.org!mit.eternal-september.org!.POSTED!not-for-mail
From: Richard <rgrdev_@gmail.com>
Newsgroups: comp.lang.c
Subject: Re: Constant strings
Date: Tue, 29 Apr 2014 09:14:14 +0200
Organization: http://www.ieee.org/
Lines: 33
Message-ID: <8738gw4ng9.fsf@gmail.com>
References: <On74v.12687$sa2.3320@fx33.am4> <hLr7v.164833$sa2.43402@fx33.am4> <bs7srkFua2rU1@mid.individual.net> <ljmnic$89u$1@speranza.aioe.org> <0.0afae8b0f55afa8aeaad.20140429011816BST.871twhyomv.fsf@bsb.me.uk> <20140428172735.291@kylheku.com> <0.85035c67accfe11b5007.20140429015837BST.87r44hx876.fsf@bsb.me.uk> <20140428180307.117@kylheku.com> <0.3ce501fc5ffd53f1c1f1.20140429031911BST.87k3a8yj1c.fsf@bsb.me.uk> <pass-by-value-20140429051143@ram.dialup.fu-berlin.de> <20140428211415.679@kylheku.com> <ljn9qm$b3n$1@speranza.aioe.org>
Mime-Version: 1.0
Content-Type: text/plain
Injection-Info: mit.eternal-september.org; posting-host="a0e0bcceb01a4703df7b4a89dec2423c"; logging-data="19760"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX1+yY6fqnjYM+JtjI1nFM8GZZnj23Vgwd+Y="
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3 (gnu/linux)
Cancel-Lock: sha1:KLE6DNFRNUxKovSb7gmu1DGghiM= sha1:Z2am8C9MM5is2XbPd5GTldQ3uzg=
Xref: csiph.com comp.lang.c:43807

glen herrmannsfeldt <gah@ugcs.caltech.edu> writes:

> Kaz Kylheku <kaz@kylheku.com> wrote:
>
> (snip)
>
>> We can easily talk, informally, about o being passed by 
>> reference (not &o, of course).
>
>> The variable o is the important value, and & is just a piece 
>> of "C fluff" to get the called function to be able to update o.
>
> Part of the design of VAX was standardized calling conventions,
> including call by value, reference, and descriptor. (And at the
> time that C was young.) 
>
> To override the default convention, you use %val(), %ref(),
> or %descr() around the appropriate argument.
>
> Seems to me, then, that VAX C should allow %ref(o) instead
> of &o, though I never tried it.
>
> Different fluff.
>
> -- glen
>

Or everyone should get over themselves and recognise &o for what it is.


-- 
"Avoid hyperbole at all costs, its the most destructive argument on
the planet" - Mark McIntyre in comp.lang.c