• 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

"TO BAD :A 1 :B" defines impossible-to-call procedure

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

#190 "TO BAD :A 1 :B" defines impossible-to-call procedure

v_6.06x
open
David Costanzo
Language Engine (245)
3
2012-12-08
2006-08-03
David Costanzo
No

From the FMSLogo manual for TO:

The default number of inputs for a procedure, which is
the number of inputs that it will accept if its
invocation is not enclosed in parentheses, is
ordinarily equal to the minimum number. If you want a
different default number you can indicate that by
putting the desired default number as the last thing on
the TO line.

Based on this, the following line should be illegal
because the default number of inputs is not the last value:

TO BAD :A 1 :B
OUTPUT LIST :a :b
END

However, this actually does define BAD, but in a way
that makes it uncallable:

BAD 1
not enough inputs to BAD
BAD 1 2
b has no value in BAD
[OUTPUT LIST :A :B]

UCBLogo 5.5 does not handle this any better
BAD 1
not enough inputs to BAD
BAD 1 2
too many inputs to BAD

In my opinion, it would be better if FMSLogo threw a
bad input error, rather than defining a procedure that
the programmer didn't intend.

How Reproducible:
Every Time

Steps to Reproduce:
TO BAD :A 1 :B

What Happens:
FMSLogo prompts you for the body of BAD

Expected Result:
TO doesn't like :B as input.

Related

Bugs: #617

Discussion


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