From: michael@kjorling.se (Michael Kjörling)
Subject: [TUHS] C declarations.
Date: Sat, 13 May 2017 12:42:47 +0000 [thread overview]
Message-ID: <20170513124247.GG9980@yeono.kjorling.se> (raw)
In-Reply-To: <0CF82AC1-E835-4C06-813F-D9EFD2C12290@tfeb.org>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 790 bytes --]
On 13 May 2017 13:35 +0100, from tfb at tfeb.org (Tim Bradshaw):
> Are there languages that copy arrays in function calls defaultly?
> Perhaps Fortran has some convention that allows that but I doubt it
> gets used very much, because it would be insane in most cases:
> COMPUTE_MEAN_TEMPERATURE(ATMOS) is really *not* going to work very
> well if it involves copying the ATMOS array.
I'm not completely sure about arrays, but at least Java has pass by
reference in some cases where you might expect pass by value. IIRC
function return values is a prime example.
--
Michael Kjörling • https://michael.kjorling.se • michael at kjorling.se
“People who think they know everything really annoy
those of us who know we don’t.” (Bjarne Stroustrup)
next prev parent reply other threads:[~2017-05-13 12:42 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-11 21:49 Ron Natalie
2017-05-11 22:01 ` Arthur Krewat
2017-05-11 23:44 ` Dave Horsfall
2017-05-11 22:03 ` David Arnold
2017-05-11 22:32 ` Larry McVoy
2017-05-11 22:41 ` Ron Natalie
2017-05-13 1:24 ` Larry McVoy
2017-05-13 2:45 ` Ron Natalie
2017-05-13 12:20 ` Michael Kjörling
2017-05-13 12:35 ` Tim Bradshaw
2017-05-13 12:42 ` Michael Kjörling [this message]
2017-05-13 15:36 ` Stephen Kitt
2017-05-14 1:59 ` Lawrence Stewart
2017-05-14 2:23 ` Dave Horsfall
2017-05-14 4:24 ` Bakul Shah
2017-05-14 6:12 ` Steve Johnson
2017-05-14 6:48 ` Bakul Shah
2017-05-14 23:06 ` Ron Natalie
2017-05-14 23:34 ` Arthur Krewat
2017-05-15 0:14 ` Dan Cross
2017-05-15 0:23 ` Ron Natalie
2017-05-15 3:43 ` Random832
2017-05-15 0:40 ` Larry McVoy
2017-05-15 2:00 ` Nevin Liber
2017-05-15 10:21 ` Tony Finch
2017-05-15 4:35 ` Dave Horsfall
2017-05-15 4:54 ` Bakul Shah
2017-05-15 5:01 ` Dave Horsfall
2017-05-15 12:58 ` Michael Kjörling
2017-05-15 16:58 ` Dave Horsfall
2017-05-15 19:00 ` [TUHS] cdecl (Re: " Bakul Shah
2017-05-15 22:52 ` Dave Horsfall
2017-05-13 13:46 ` [TUHS] " Hellwig Geisse
2017-05-13 19:08 ` Random832
2017-05-13 23:21 ` Dave Horsfall
2017-05-14 14:48 ` Nemo
2017-05-13 19:05 ` Random832
2017-05-14 13:14 ` Derek Fawcus
2017-05-12 0:15 ` Bakul Shah
2017-05-12 2:41 ` Theo Pavlidis
2017-05-12 14:04 Richard Tobin
2017-05-13 23:11 Richard Tobin
2017-05-15 6:46 ` Tim Bradshaw
2017-05-14 14:11 Doug McIlroy
2017-05-14 14:58 ` Steve Nickolas
2017-05-15 18:47 Steve Johnson
2017-05-15 19:54 ` Bakul Shah
2017-05-16 7:25 ` George Ross
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170513124247.GG9980@yeono.kjorling.se \
--to=michael@kjorling.se \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).