Guarding against uninitialized variables RFC

[chris hermansen]

Good day everyone,

After 10 days away from almost everything to do with computers in order to
concentrate on Important Stuff (like beaches), I'm back prodding van
Vliet's transput.

The open, establish and create procedures will fail with a non-zero return
code if they cannot establish the linkage between File, Channel, Book and
the operating system file.  However this can leave the nonpublic Book
variable in an uninitialized state.

Of course, I can initialize the Book variable to some pattern that I can
later interpret as meaning no linkage was created; and I can check wherever
that Book variable is used to make sure it has a valid linkage.

But I don't believe there is a way to detect uninitialized variables other
than this.

Does anyone have any suggestions?  Thanks in advance!

-- 
Chris Hermansen · clhermansen "at" gmail "dot" com

C'est ma façon de parler.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://gcc.gnu.org/pipermail/algol68/attachments/20260621/ffee4220/attachment-0001.htm>