* [edbrowse-dev] comma-separated return statements
@ 2019-07-21 6:11 Kevin Carhart
0 siblings, 0 replies; only message in thread
From: Kevin Carhart @ 2019-07-21 6:11 UTC (permalink / raw)
Wow, I should have looked this up many days ago. There's a phrasing
created by minimization which is misleading for human readers.
FYI if you don't already know, in the compound return statement,
The a,b,c are simply going to be run. The real return value is the d. It
is not somehow a compound value which draws from all of them because that
isn't how return works.
So return a,b,c,d is functionally the same as
And this means that there can be a chance to echo values in between those
lines. Otherwise, I thought I was stuck with these impenetrable blocks
that became illegal if you break them up.
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2019-07-21 6:11 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2019-07-21 6:11 [edbrowse-dev] comma-separated return statements Kevin Carhart
edbrowse-dev - development list for edbrowse
This inbox may be cloned and mirrored by anyone:
git clone --mirror http://inbox.vuxu.org/edbrowse-dev
# If you have public-inbox 1.1+ installed, you may
# initialize and index your mirror using the following commands:
public-inbox-init -V1 edbrowse-dev edbrowse-dev/ http://inbox.vuxu.org/edbrowse-dev \
Example config snippet for mirrors.
Newsgroup available over NNTP:
AGPL code for this site: git clone https://public-inbox.org/public-inbox.git