Re: CLIPPED in 4GL behaving differently in latest rev

Candy, Had the exact same problem on HP/UX10.20 I4GL 7.20. As to whether it is an intended feature or a developers glitch, I couldn't say. I worked around it by appending the ASCII 13 after the CLIPPED. Or I guess you could simply display positions 1 through 32 and drop the annoying CLIPPED. HTH Chris "Candy McCall" <candym@olcinc.com> on 28/06/99 22:11:54 To: "Informix List" <informix-list@iiug.org> cc: (bcc: Chris West/Finance/MEDAS) Subject: CLIPPED in 4GL behaving differently in latest rev We are currently using I4GL 7.20.UD1. In some of our reports, we output a Carriage Return at the end of a line. In order to do this, we assign the value ASCII 13 to the end of a character buffer containing the line to be outputted. Then, when the line is printed, we clip the line. In the following program, testcr.4gl, if you run testcr.4ge>test.out, you will only see a ^M at the end of the first line. The second line will clip the carriage return. In previous revisions of 4GL, it did not clip the carriage return. Also, under D4GL, it does not clip the carriage return (it prints two lines with ^M at the end of each). Has anyone else had problems with this and is this a bug? Thanks! Candy -- Candy McCall ONLINE Computing, Inc. (candym@olcinc.com) testcr.4gl: main define p_string char(32), i smallint for i = 1 to 32 let p_string[i,i] = " " end for let p_string[1,32] = "test" let p_string[32,32] = ASCII 13 display p_string display p_string clipped end main ~