Re: Queries

[Sam S. <sd...@gn...>]

> * Compro Prasad <pbzcebcenfnq@tznvy.pbz> [2017-05-22 20:27:22 +0500]:
>
> What do the following file naming conventions refer to:
> + spvw*

the second line of spvw.d says:

 * (SPVW = Speicherverwaltung): Memory Management for CLISP

> + clos*

the first line of clos.lisp says:

;;;; Common Lisp Object System for CLISP

https://en.wikipedia.org/wiki/Common_Lisp_Object_System

> + ari*

search for NO_ARI_ASM in lispbibl.d:

       Hand-written assembler code for arithmetic, especially multi-precision
       arithmetic:
         NO_ARI_ASM

> + *.d (why not the default *.c)

CLISP pre-processes those into normal C
https://sourceforge.net/p/clisp/mailman/message/35596028/

there are 3 preprocessors:

1. comment5: replaces "# " shell-style comments with /**/ C comments
   --- should be removed

2. varbrace: surrounds "var int foo" declarations with braces.
   --- should be removed

3. gctrigger: instruments "maygc" function so catch GC-safety bugs at
   run time (http://clisp.org/impnotes/gc-safety.html#gc-alloccount)
   --- must be kept!

You can search ML archives
(https://sourceforge.net/p/clisp/mailman/search/?q=preprocessing&sort=posted_date+desc&limit=250)
for more information.

Basically, we need to remove varbrace & comment5 and replace *.d with
*.c and gctrigger should write *.m.c and gcc should compile them to *.o.

http://www.cygwin.com/acronyms/#PTC


-- 
Sam Steingold (http://sds.podval.org/) on darwin Ns 10.3.1504
http://steingoldpsychology.com http://www.childpsy.net
http://iris.org.il http://islamexposedonline.com http://www.dhimmitude.org
Do not tell me what to do and I will not tell you where to go.