9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Jeremy Fitzhardinge jeremy@sour.sw.oz.au
Subject: Alef questions
Date: Fri,  4 Aug 1995 02:34:48 -0400	[thread overview]
Message-ID: <19950804063448.eVkw6XuqFsAd5NEEBOdbfVABJX3Gzk5YKc3RJFroKrI@z> (raw)

philw@plan9.att.com:
> Tuples are
> evaluated by generating the address of the lval and then evaluating
> each member directly into the destination. If there is no lval the
> expression is thrown away.

If it's not a bug, it's very surprising.  Even if you throw away
a value, you expect the side-effects to happen.  I was kind of
expecting it to work, since it would effectively recover the comma
operator: you get the general form where you can use or throw away
any of the expressions.

	J






             reply	other threads:[~1995-08-04  6:34 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1995-08-04  6:34 Jeremy [this message]
  -- strict thread matches above, loose matches on Subject: below --
1995-10-25 15:22 bobf
1995-10-25  7:47 Christopher.Vance
1995-10-25  7:41 Hans-Peter
1995-10-25  7:13 Christopher.Vance
1995-08-04 15:25 philw
1995-08-03 15:39 philw
1995-08-03  8:17 Jeremy

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=19950804063448.eVkw6XuqFsAd5NEEBOdbfVABJX3Gzk5YKc3RJFroKrI@z \
    --to=9fans@9fans.net \
    /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).