• Join/Login
  • Business Software
  • Open Source Software
  • For Vendors
  • Blog
  • About
  • More
    • Articles
    • Create
    • SourceForge Podcast
    • Site Documentation
    • Subscribe to our Newsletter
    • Support Request
SourceForge logo
For Vendors Help Create Join Login
SourceForge logo
Business Software
Open Source Software
SourceForge Podcast
Resources
  • Articles
  • Case Studies
  • Blog
Menu
  • Help
  • Create
  • Join
  • Login
  • Home
  • Browse
  • FMSLogo
  • Bugs
FMSLogo

Logo doesn't evaluate up to point of error for some errors

A Logo programming environment for Microsoft Windows

Brought to you by: david_costanzo
  • Summary
  • Files
  • Reviews
  • Support
  • Tickets ▾
    • Feature Requests
    • Bugs
    • Support Requests
  • Discussion
  • Code
Menu ▾ ▴
  • Create Ticket
  • View Stats

Group

  • v_6.06x
  • v_6.07.X
  • v_6.08.X
  • v_6.10.X
  • v_6.11.X
  • v_6.13.X
  • v_6.22.X
  • v_6.25.X
  • v_6.26.X
  • v_6.27.X
  • v_6.28.X
  • v_6.29.X

Searches

  • Changes
  • Closed Tickets
  • Open Tickets

Help

  • Formatting Help

#481 Logo doesn't evaluate up to point of error for some errors

v_6.06x
closed-duplicate
nobody
None
1
2026-08-11
2016-07-23
David Costanzo
No

FMSLogo generally runs all instructions up to the point of an error. However for some, it stops running instructions before it gets to the problem. This brings some implementation details into the language specification. It would be better if the errors were treated the same.

The bug can be seen by running the following procedure

To ShowBug

  make "x 0
  make "y 0
  make "z 0

  CATCH "ERROR [
    make "x 1
    IGNORE (UnknownProc [255 0 0])
  ]

  CATCH "ERROR [
    make "y 1
    IGNORE (REMAINDER 1 2 3)
  ]

  CATCH "ERROR [
    make "z 1
    IGNORE (REMAINDER 1)
  ]

  SHOW (se [x =] :x [, y =] :y [, z =] :z)

End

Each of the CATCH blocks has a valid instruction with a detectable side effect, followed by one that throws an error. So you'd think that they'd all behave the same. However when run only the following is printed:

showbug
[x = 0 , y = 0 , z = 1]

This indicates that the "unknown parameters" and the "too many inputs" errors somehow prevented the instructions before it from running, whereas the "not enough inputs" didn't.

Discussion

  • David Costanzo

    David Costanzo - 2026-08-11
    • status: open --> closed-duplicate
     
    If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
  • David Costanzo

    David Costanzo - 2026-08-11

    When the instructions are all on different lines, this is a duplicate of Bug #250.
    This bug has been fixed, so the repro steps in the description no longer reproduce any problem.

    When the instructions are on the same line, this is a duplicate of Bug #625.

     

    Related

    Bugs: #250
    Bugs: #625

    If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Log in to post a comment.

SourceForge
  • Create a Project
  • Open Source Software
  • Business Software
  • Top Downloaded Projects
Company
  • About
  • Team
  • SourceForge Headquarters
    1320 Columbia Street Suite 310
    San Diego, CA 92101
    +1 (858) 422-6466
Resources
  • Support
  • Site Documentation
  • Site Status
  • SourceForge Reviews
SourceForge logo
© 2026 Slashdot Media. All Rights Reserved.
Terms Privacy Opt Out Advertise
MongoDB Logo MongoDB