Important Notice: Our web hosting provider recently started charging us for additional visits, which was unexpected. In response, we're seeking donations. Depending on the situation, we may explore different monetization options for our Community and Expert Contributors. It's crucial to provide more returns for their expertise and offer more Expert Validated Answers or AI Validated Answers. Learn more about our hosting issue here.

Why does CLISP insist on interpreting command line options passed to my executable?

April 26, 2017clisp Command executable insist interpreting line Options

0

Posted

Why does CLISP insist on interpreting command line options passed to my executable?

1 Answer

0

Posted

When you run a stand-alone executable created with (EXT:SAVEINITMEM “foo” :executable t :script t :init-function #’start-me), you might want all command line options to end up in EXT:*ARGS* for your start-me function to process. This is not the case. The options are still processed by CLISP (see Section 31.1.1, “Cradle to Grave”).