Results 1 to 3 of 3

Thread: #run error_level

Hybrid View

Previous Post Previous Post   Next Post Next Post
  1. #1

    Default #run error_level

    I'm using the #run compiler directive to execute AmalgamateFiles.cmd.
    If it fails, it sets the DOS error_level to 1, but I cannot determine
    how to trap that using #run.

    Do I need to have my cmd write it to an INI file, then use #getini to
    read it?

    Mike Hanson
    www.boxsoft.net

  2. #2

    Default Re: #run error_level

    Mike, Mike, Mike, <g>

    > I'm using the #run compiler directive to execute AmalgamateFiles.cmd.
    > If it fails, it sets the DOS error_level to 1, but I cannot determine
    > how to trap that using #run.

    RTFM!

    If the function succeeds, the SB_ERROR preprocessor symbol value is
    zero.

    If the function fails, the SB_ERROR preprocessor symbol value is
    nonzero.

    The compiler can catch the "#run..." exit code in the built-in
    "SB_ERROR" compiler variable.

    --
    Lee White

    RPM Report Viewer.: http://www.cwaddons.com/products/rpm/
    Report Faxing.....: http://www.cwaddons.com/products/afe/
    ---Enroll Today---: http://CWaddons.com

    Creative Reporting: http://www.CreativeReporting.com

    Product Release & Update Notices
    http://twitter.com/DeveloperPLUS

  3. #3

    Default Re: #run error_level

    LOL!

    Thanks, Lee. In the meantime I coded it to use an INI file, and
    extended it to display the text error message in the SB compile log.

    Mike Hanson
    www.boxsoft.net

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •