In article <2l85biINNqks@emory.mathcs.emory.edu> walt@mathcs.emory.edu (Walt Hultgren {rmy}) writes:
>From: walt@mathcs.emory.edu (Walt Hultgren {rmy})
>Subject: Re: Strings in compiled forms
>Date: 4 Mar 1994 15:23:14 -0500
>In article <jolomoCM06xG.37y@netcom.com> jolomo@netcom.com (Joe Morris) writes:
>>Hello,
>> My site uses sccs for our version control and I'm forcing everyone
>>to embed string commands in their 4gls so that the 'what' command
>>will tell me which versions of the 4gls are in a compiled 4ge.
>> Does anyone know of a good way to implement this in forms?
>We also use SCCS and have this same requirement, but I have yet to come up
>with any solutions I'm completely satisfied with.
>When you say that you don't want to place the SCCS info in "the" screen
>section, do you mean the one that 4GL users see, or *any* screen section in
>the form? form4gl will compile a multi-screen form, so you can define a
>dummy second screen with the SCCS string in it. It will be placed in the
>".frm" file, but the 4GL program won't use it. The drawback to this
>approach is that form4gl will create a ".err" file, issue a warning, and
>exit with a non-zero status. This is kind of a hassle when you're using
>make.
Why noy put in a comment right before any of the screens. Anything within {}
is a comment also I believe you can use #. See the manuals for that. I 've
tried that technique and it works just fine. The users never see it.