Uploaded image for project: 'HPCC'
  1. HPCC
  2. HPCC-21047

Examples of LOOP in Ref manual do not tie up with the order of the 'Forms' of LOOP

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Not specified
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 7.0.6
    • Component/s: Documentation
    • Labels:
      None

      Description

      Hi,

      I'm still battling with the LOOP command, and mistakes in the documentation don't help.

      1. Example 'Form 1' Uses a Boolean expression as its control. But the 'Form 1' of the LOOP documentation is 'loopcount' which in an Integer expression.
      2. Example 'Form 4' Only has a single 'rowfilter' . But the 'Form 4' of the LOOP documentation is 'rowfilter','loopcondition', i.e. two controls.
      3. Example 'Form 5' Does have parameters as documented for Form 5, but its not clear why this example is a 'loopfilter' and not a 'rowfilter' especially as it is 'LEFT.age < 100
      4. It's not at all clear from the Ref manual documentation how the distinction is made between 'loopfilter' and 'rowfilter'. They do the opposite of each other, one for specifying records that are NOT yet complete, the Other  specifying records that ARE complete. I can't tell the difference and I don't know how the compiler can as well.

      My personal view is that the whole section on LOOP in the Ref manual needs to be rewritten from scratch. It seems to me to be a very useful built-in, but I don't see its use in any of our code, presumably because people can't get their head round how to drive it.

      Yours

      Allan  

        Attachments

          Activity

            People

            • Assignee:
              jamesdefabia Jim DeFabia
              Reporter:
              allan Allan Francis Wrobel
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: