BREAK Statement

BREAK [number]

Inserts a soft breakpoint or debugger breakpoint at the beginning of next statement.  When running under a debugger, the debugger will break at the next statement.  Without the debugger, the error handler will be called with a breakpoint condition.  A Trace message will also be sent.  Note that Trace has to be turned on in order for the BREAK statement to have an affect without using a debugger.

Example:

OPTION EXPLICIT ON

OPTION TRACE ON

' Should have MyBASIC2_Inc Environment Variable Defined

$INCLUDE "MyBASIC2_C3DFile"

' Need to use C3D Extension Libraries

$LIBRARY "MyBASIC2_C3DLib.dll"

$LIBRARY "MyBASIC2_C3DFileLib.dll"

DIM nFile AS INTEGER

DIM i AS INTEGER

DIM j AS INTEGER

DIM strName AS STRING

DIM fid AS HANDLE

nFile = C3DFile.Create( "e:\123.c3d", "Kalle Ankas File", "bits", 10, 3, 100, 2, 200 )

BREAK 123

IF nFile <> 0 THEN

  strName = "Kalle Anka was here with Nils today"

  C3DFile.CreateParameter( nFile, "POINT:KALLE", TYPE( strName ), LEN( strName ), 0, 0 )

  C3DFile.SetParameter( nFile, "POINT:KALLE", strName )

  i = 123

  C3DFile.CreateParameter( nFile, "POINT:NISSE", TYPE( i ) )

  C3DFile.SetParameter( nFile, "POINT:NISSE", i )

  C3DFile.SetPointName( nFile, 1, "Kalle" )

  C3DFile.SetPointName( nFile, 2, "Nisse" )

  C3DFile.SetPointName( nFile, 3, "Pelle" )

ENDIF

This will display the following dialog when running under the MyBASIC2 Ide