Re: Thoughts on the simplification of CLISP
Sam Steingold <[email protected]>
| Newsgroups | gmane.lisp.clisp.devel |
|---|---|
| Message-ID | <[email protected]> |
> * Pascal Bourguignon <[email protected]> [2017-01-10 23:28:25 +0100]: > >> On 10 Jan 2017, at 22:16, Sam Steingold <[email protected]> wrote: >> >> I think we need to drop the gratuitous preprocessors (varbrace & >> comment5) and rename all files to *.c. >> We need to preprocess them into *.m.c behind the scenes. >> lisbpbibl.d should be lisbpbibl.h and not preprocessed. >> &c. > > Well, I both agree and disagree. > > > Pure C code is good, and it would be great for portability, if one could > write 100% purely standard C11 code. I never proposed removing assembly &c. > Like, no trick like libsigsegv, or worse ffcall/avcall which can never > be compiled on new or exotic systems. > Just pure standard entirely defined behavior C11 code. I am certainly not proposing that. If you look at a previous message, I explain the gctrigger preprocessor and why it is desirable. What I am opposed to is "gratuitous syntax modifications". -- Sam Steingold (http://sds.podval.org/) on darwin Ns 10.3.1504 http://steingoldpsychology.com http://www.childpsy.net https://jihadwatch.org http://camera.org http://www.dhimmitude.org http://iris.org.il Do not worry about which side your bread is buttered on: you eat BOTH sides. ------------------------------------------------------------------------------ Developer Access Program for Intel Xeon Phi Processors Access to Intel Xeon Phi processor-based developer platforms. With one year of Intel Parallel Studio XE. Training and support from Colfax. Order your platform today. http://sdm.link/xeonphi _______________________________________________ clisp-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/clisp-devel