Skip navigation

DO/ENDDO break statement

Help

DO/ENDDO break statement

Tagged:
Implemented
Assigned to bob.stone
Wednesday, May 13
High
Enhancement
1 year 20 weeks ago

Among the high level parts DO...ENDDO, is often used. It is also often needed to break out from the loop using a conditional IF statement together with JUMPTO. Though JUMPTO statements can be used and sometimes is the best solution, a BREAK statement is missed in DMIS. "Break" command is found in many programming languages and in a way carries out the same functionality as JUMPTO, but does it in slightly different way that in the end makes a lot of difference. For example Sandvik milling cutting tools have repeated operations in each insert seat. When the "DMIS-code" is copied, or rather reproduced for all insert seats, breaking out of DO...ENDDO causes ambiguities, since the JUMPTO target label is also copied and thus the same target label will exist at many locations in the program. Then it becomes ambiguous to which target label should the CMM actually jump.

QIF Groups: 
QIF Execution
Login or register to view attached files

#1

Assigned: Unassigned » bob.stone

From Sandvik

#2

Status: Open » In-Work

Assigned to DMIS/QIFExecution for implementation

#3

Status: In-Work » Vote Pending

Implemented in 5.3 draft document with wording changes,

#4

Status: Vote Pending » Implemented

Implemented in 5.3 at UTARI Meeting.

Ray Admire

DMIS
Need help?

Case Tracker

The case tracker gives you a way to track progress on your projects and assign cases to yourself and others.

  • Add projects to keep your cases organized.
  • Add cases to assign tasks or assignments to yourself and others for completion.
  • Cases can be reassigned, postponed, and closed, among other actions.
  • The history of a case - who it's been assigned to, its status and its priority - can be tracked viewing its comment thread.