• 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

GENSYM exposes the variable gensym.number

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

#595 GENSYM exposes the variable gensym.number

v_6.06x
closed-fixed
nobody
None
5
2025-02-19
2025-01-25
DanielAjoy
No

Hi,

If I run the command GENSYM I expect to get a unique word.

I do get a unique word, however, the environment now has a variable called gensym.number

That is not documented as an expected behavior, and I opened this ticket so that gensym.number is buried by GENSYM...

but maybe it shouldn't be, because when we save the environment and load it at a later time we might want to keep guaranteeing unique words. I believe this is an unlikely use of this command.

I'm leaning towards:

  • GENSYM should bury gensym.number
  • The documentation should say something along the lines of:

"Outputs a unique word each time it is invoked during the current session. The words are of the form G1, G2, etc. When a fresh session is open the counter restarts at 1"

Discussion

  • David Costanzo

    David Costanzo - 2025-01-31
    • status: open --> open-accepted
     
    If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
  • David Costanzo

    David Costanzo - 2025-01-31

    UCBLogo 6.2.3 buries the variable and I don't see any plausible compatibility problems in doing that.

    Your proposed update to the documentation sounds reasonable, too.

    It's interesting that the names are documented as "G1, G2, etc." but generated as lowercase "g1, g2, etc.". I wonder if there's a story behind that. I may change the documentation to match the implementation.

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

    David Costanzo - 2025-02-19
    • status: open-accepted --> closed-fixed
     
    If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
  • David Costanzo

    David Costanzo - 2025-02-19

    This is fixed by [r6087], which buries gensym.number. The help entry was also fixed, along the lines you suggested.

    The fix will be available in whatever version follows 8.4.0.

     

    Related

    Commit: [r6087]

    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
mdb logo