Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!rutgers!sri-unix!ctnews!pyramid!decwrl!decvax!ucbvax!noah.arc.CDN!kenw
From: kenw@noah.arc.CDN (Ken Wallewein)
Newsgroups: comp.os.vms
Subject: C++ operator overloading
Message-ID: <48*kenw@noah.arc.cdn>
Date: Sat, 25-Apr-87 18:21:46 EDT
Article-I.D.: noah.48*kenw
Posted: Sat Apr 25 18:21:46 1987
Date-Received: Sun, 26-Apr-87 22:37:39 EDT
Sender: daemon@ucbvax.BERKELEY.EDU
Distribution: world
Organization: The ARPA Internet
Lines: 25


  Maybe this isn't the correct forum, but I don't know of a better one, so...
I have been watching with great interest any news on C++. Haven't seen any
articles, yet, which surprises me. However, I recently read a copy of the
OASYS' Designer C++ Technical Specifications. It allows function and operator
overloading, and I have one key question:

  Does allowable operator overloading include the assignment (=) operator?

A long time ago I became frustrated with the inability to perform such things
as file I/O by assignment, e.g. 
	file2.record1 = file1.record3.
I can say
	a = input(file1,record1)
but I can't say 
	output(file1,record1) = a.
I think external storage should be treated as much as possible the save way as
internal storage. Ever heard of virtual arrays (the RSTS Basic+ kind, not the
RSX FORTRAN77 kind)? Vax global sections are a clumsy approach to this concept.

  I'm not sure - maybe I still need something I have in the past referred to
as read/write functions... The only language I can think of at the moment that
supports this is Icon by Ralph Griswold of Snobol4 fame.
  Anyway, I'm now pinning my hopes on C++ assignment operator overloading. 
/kenw