!standard B.3.1    (44)                               96-06-05  AI95-00039/02
!class binding interpretation 95-06-25
!status WG9 approved 95-06-14
!status ARG approved 11-0-0 (by letter ballot) 96-06-05
!status ARG approved (subject to letter ballot) 9-0-1  95-11-01
!status received 95-06-25
!subject Effect of Update(Null_Ptr,...)

!summary 95-06-25

Interfaces.C.Update raises Dereference_Error if Item = Null_Ptr.

!question 95-06-25

Does Update raise Dereference_Error if Item = Null_Ptr? (Yes.)

!recommendation 95-06-25

Interfaces.C.Update raises Dereference_Error if Item = Null_Ptr.

!wording 95-06-25

!discussion 95-06-25

This seems like the only sensible semantics.

!appendix 95-06-25

!section B.3.1(44)
!subject Effect of Update(Null_Ptr,...)
!reference RM95-B.3.1(44)
!from Norman Cohen
!reference as: 95-5119.d Norman H. Cohen 95-4-7>>
!discussion

Does Update raise Dereference_Error if Item = Null_Ptr?

****************************************************************

!section B.3.1(44)
!subject Effect of Update(Null_Ptr,...)
!reference RM95-B.3.1(44)
!reference 95-5119.d Norman Cohen 95-04-07
!from Tucker Taft 95-04-12
!reference as: 95-5127.d Tucker Taft 95-4-12>>
!discussion

> Does Update raise Dereference_Error if Item = Null_Ptr?

Presumably, to be consistent with Strlen and Value.
You could argue that the line "Let N = Strlen(Item)" in B.3.1(45)
implies that if Strlen propagates Dereference_Error, then so does
Update.  However, being a bit more explicit would help.

-Tuck

****************************************************************