Return to the
comp.compilers page.
Search the
comp.compilers archives again.
| Related articles |
|---|
| Designing a language for dataflow/parallelism tony@tonyRobinson.com (2005-06-13) |
| Re: Designing a language for dataflow/parallelism torbenm@diku.dk (2005-06-16) |
| Re: Designing a language for dataflow/parallelism nmm1@cus.cam.ac.uk (2005-06-16) |
| Re: Designing a language for dataflow/parallelism mailbox@dmitry-kazakov.de (Dmitry A. Kazakov) (2005-06-16) |
| Re: Designing a language for dataflow/parallelism rand@rice.edu (Randy) (2005-06-18) |
| Re: Designing a language for dataflow/parallelism gneuner2@comcast.net (George Neuner) (2005-06-18) |
| Re: Designing a language for dataflow/parallelism peteg42@gmail.com (Peter Gammie) (2005-06-19) |
| Re: Designing a language for dataflow/parallelism gneuner2@comcast.net (George Neuner) (2005-06-21) |
| Designing a language for dataflow/parallelism peteg42@gmail.com (Peter Gammie) (2005-06-26) |
| From: | "Dmitry A. Kazakov" <mailbox@dmitry-kazakov.de> |
| Newsgroups: | comp.compilers |
| Date: | 16 Jun 2005 00:08:07 -0400 |
| Organization: | cbb software GmbH |
| References: | 05-06-081 |
| Keywords: | parallel |
| Posted-Date: | 16 Jun 2005 00:08:07 EDT |
On 13 Jun 2005 17:57:19 -0400, tony@tonyRobinson.com wrote:
> Even perhaps a memory type that only allows one reference and
> automatically takes the prior reference out of scope, as in:
If a memory type allows only one reference, why to talk about references?
The object in that memory will be isomorphic to the reference, i.e. there
will be no difference between them. Call reference "object" and forget
about pointers.
--
Regards,
Dmitry A. Kazakov
http://www.dmitry-kazakov.de
Return to the
comp.compilers page.
Search the
comp.compilers archives again.