On Wednesday, 13 March 2019 03:03:17 UTC,
[email protected] wrote:
On Wednesday, February 27, 2019 at 9:01:19 AM UTC+8, Buck wrote:
On Tuesday, February 26, 2019 at 2:18:58 AM UTC-5, [email protected] wrote:
HI DO YOU HAVE A SIMPLE EXAMPLE FOR LEVEL BREAK IN EXTERNALLY DESC PRINTER FILE?
There is nothing special about level breaks and printer files. Just WRITE the appropriate record format at the appropriate time, for example
if *inl1;
write l1Detail;
endif;
Total time is a bit harder, because if can't be done in /free; you'll need a genuine C-specification:
Cl1 write l1Total
Hope that helps.
--buck
Can we have statement before do loop ? Im putting 01 at conditioning indicator and do at operation. When I try to debug after the enddo it will go back to the statement before the do. Can i know why ?
I personally never liked conditioning indicators on if or do statements. What does it mean? Turn only the condition on or off or the whole code block?
When computers only had a few kilobytes of memory this form of programming was well matched to the limited resources, but nowadays you should probably re-write from scratch.
One thing which I have seen a lot of is that the program object and source code do not match. This often makes the line numbers not line up, and so the program loops back to a different line in the program source. If you dont know how do "dspobjd library/
program *pgm" and note the change date & time. Then "dspfd library/sourcefile" and note the date & time of the member.
If you are using modules then dsppgm will give you info on these.
My advice, post your question and a snippet of your code into a new thread. This might entice people to look at it instead of spotting its a 19 year old thread and going somewhere else.
Jonathan
--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)