Skip to Main Content
HCL Domino Ideas Portal

Welcome to the #dominoforever Product Ideas Forum! The place where you can submit product ideas and enhancement request. We encourage you to participate by voting on, commenting on, and creating new ideas. All new ideas will be evaluated by HCL Product Management & Engineering teams, and the next steps will be communicated. While not all submitted ideas will be executed upon, community feedback will play a key role in influencing which ideas are and when they will be implemented.

For more information and upcoming events around #dominoforever, please visit our Destination Domino Page

Status Needs Review
Workspace Domino Designer
Categories LotusScript
Created by Guest
Created on May 30, 2023

Add preference for NOT using Option Public in LotusScript Agents and Script Libraries

I would like a preference to NOT use Option Public in LotusScript Agents and Script Libraries. It forces the developer to make things that can be shared explicitly Public, and promotes thinking abou what should be Public and what should be Private.

A smaller Public interface has a smaller chance of becoming spaghetti code, which is hard to debuig and maintain.

  • Attach files
  • Guest
    Jun 21, 2023

    Do not use Option Public.

    If this is not specified, then all elements of the library will be Private by default. And then for public elements, you will need to explicitly specify Public Sub, Public Function, etc.

    I don't understand what is the problem?

  • Guest
    Jun 1, 2023

    Agreed. Anyway, I never understood how Option Public can make sense for a LotusScript agent. AFAIK there is no way how agent code can be shared by any other design element.