From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me
X-Spam-Level: 
X-Spam-Status: No, score=-0.6 required=5.0 tests=BAYES_00,FREEMAIL_FROM,
	FROM_STARTS_WITH_NUMS,INVALID_MSGID autolearn=no autolearn_force=no
	version=3.4.4
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: 103376,47bd5b7b3b898723
X-Google-Attributes: gid103376,public
From: Rex Reges <73653.1634@CompuServe.COM>
Subject: Re: Form feed comment for pragma Page
Date: 1996/06/12
Message-ID: <4pl7j0$1mc$2@mhafn.production.compuserve.com>#1/1
X-Deja-AN: 159709707
references: <4pl5t9$1mc$1@mhafn.production.compuserve.com>
organization: CompuServe, Inc. (1-800-689-0736)
newsgroups: comp.lang.ada
Date: 1996-06-12T00:00:00+00:00
List-Id: <comp.lang.ada>


I was cut off! Sorry about that. As I was saying...

One should not put a null character in a comment since the Unix 
debuggers tend to stop printing when they encounter a null.
For example, when I examine strings while debugging, I have found 
that the full string will not be printed if a null is embedded:

    Example : Strin(1..7) ;
    Example := "ABC" & Character'Val(000) & "DEF" ;

Examinging Example will result in:
 
    Example = "ABC"

In addition, useful tools like Vax's CMS won't accept some control 
characters inthe source code (at least the old versionI am using).  

Therefore, my recommendation is to stick to the visible character 
set including foreign characters which AI-00339 was actually aimed 
at. Also, when debugging, examine strings in hex first to see if any
nulls are lurking about.

-- 
or you can call me The Fixer...
or you can e-mail me at RegesR@pgate.he.boeing.com