From jkr@jkr.cc.rl.ac.uk  Tue May 15 17:10:38 2001
Received: from nameserv.rl.ac.uk (nameserv.rl.ac.uk [130.246.135.129])
	by dkuug.dk (8.9.2/8.9.2) with ESMTP id RAA46514
	for <SC22WG5@dkuug.dk>; Tue, 15 May 2001 17:10:37 +0200 (CEST)
	(envelope-from jkr@jkr.cc.rl.ac.uk)
Received: from jkr.cc.rl.ac.uk (jkr.cc.rl.ac.uk [130.246.8.20])
	by nameserv.rl.ac.uk (8.8.8/8.8.8) with ESMTP id QAA22934
	for <SC22WG5@dkuug.dk>; Tue, 15 May 2001 16:11:00 +0100
Received: (from jkr@localhost)
	by jkr.cc.rl.ac.uk (8.8.8+Sun/8.8.8) id QAA19871
	for SC22WG5@dkuug.dk; Tue, 15 May 2001 16:13:08 +0100 (BST)
Date: Tue, 15 May 2001 16:13:08 +0100 (BST)
From: John Reid <jkr@rl.ac.uk>
Message-Id: <200105151513.QAA19871@jkr.cc.rl.ac.uk>
To: SC22WG5@dkuug.dk
Subject: Re: (SC22WG5.2061) Interp F90/204
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"

> 
> Am I correct that in the current and draft standards users cannot write 
> procedures whose arguments have the semantics of intrinsic assignment, and 
> hence cannot write a MVBITS of their own? If I am correct, has there been any 
> request for this capability?

It is permitted to overload assignment for a derived type, in which
case default assignment is not available for that type. I do not
see how this is relevant to MVBITS. Yes, a user can write a MVBITS of
his or her own. 

John.