Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • D Demonstrator - Reasoning WebAPI
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 4
    • Issues 4
    • List
    • Boards
    • Service Desk
    • Milestones
  • Deployments
    • Deployments
    • Releases
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • cogsys
  • Dare2Del
  • Demonstrator - Reasoning WebAPI
  • Issues
  • #26

Closed
Open
Created Nov 24, 2020 by Siebers, Michael@michael.siebersOwner

Startup parameters

Startup options for the server (like port to run on) seem to be managed in the predicate server_opts/1. However, I do not use how to use them. Regarding the port option, for instance, neither of the following works:

swipl -s run.pl --port 8976
swipl -s run.pl --port=8976
swipl -s run.pl port=8976

According to the swipl usage message, swi-options and programm arguments should (can?) be separated by --. This seems to kinda work. However, then our code complains that -- is no valid argument.

Basically, I have the following questions:

  1. How is it possible to start the server with arguments?
  2. Which arguments are defined? Or rather, what do they do?
  3. Can we print some usage message ourselves? For example with -h but without interfering with swipl's -h argument?
Assignee
Assign to
Time tracking