Re: [scheme-reports-wg2] Threads and futures
Linas Vepstas
(19 Mar 2022 05:54 UTC)
|
Re: [scheme-reports-wg2] Threads and futures
Marc Nieper-Wißkirchen
(19 Mar 2022 08:24 UTC)
|
Re: [scheme-reports-wg2] Threads and futures
John Cowan
(19 Mar 2022 18:57 UTC)
|
Re: [scheme-reports-wg2] Threads and futures
Linas Vepstas
(19 Mar 2022 20:04 UTC)
|
Re: [scheme-reports-wg2] Threads and futures
Marc Nieper-Wißkirchen
(19 Mar 2022 22:11 UTC)
|
Re: [scheme-reports-wg2] Threads and futures
Linas Vepstas
(20 Mar 2022 07:50 UTC)
|
Re: [scheme-reports-wg2] Threads and futures
John Cowan
(20 Mar 2022 22:34 UTC)
|
Re: [scheme-reports-wg2] Threads and futures
Marc Feeley
(21 Mar 2022 04:49 UTC)
|
Re: [scheme-reports-wg2] Threads and futures
Marc Nieper-Wißkirchen
(21 Mar 2022 06:28 UTC)
|
Re: [scheme-reports-wg2] Threads and futures
Marc Nieper-Wißkirchen
(21 Mar 2022 06:54 UTC)
|
Re: [scheme-reports-wg2] Threads and futures
Ray Dillinger
(21 Mar 2022 19:00 UTC)
|
Re: [scheme-reports-wg2] Threads and futures
Dr. Arne Babenhauserheide
(21 Mar 2022 16:54 UTC)
|
Re: [scheme-reports-wg2] Threads and futures
Marc Nieper-Wißkirchen
(21 Mar 2022 16:04 UTC)
|
Re: [scheme-reports-wg2] Threads and futures
Taylan Kammer
(23 Mar 2022 14:20 UTC)
|
Re: [scheme-reports-wg2] Threads and futures
Marc Nieper-Wißkirchen
(23 Mar 2022 14:28 UTC)
|
Re: [scheme-reports-wg2] Threads and futures
Dr. Arne Babenhauserheide
(23 Mar 2022 15:40 UTC)
|
Re: [scheme-reports-wg2] Threads and futures
Marc Nieper-Wißkirchen
(23 Mar 2022 15:34 UTC)
|
Re: [scheme-reports-wg2] Threads and futures
Dr. Arne Babenhauserheide
(23 Mar 2022 22:08 UTC)
|
Re: [scheme-reports-wg2] Threads and futures
Ray Dillinger
(01 Apr 2022 23:04 UTC)
|
Re: [scheme-reports-wg2] Threads and futures Per Bothner (01 Apr 2022 23:21 UTC)
|
Re: [scheme-reports-wg2] Threads and futures
Ray Dillinger
(01 Apr 2022 23:28 UTC)
|
Re: [scheme-reports-wg2] Threads and futures
Per Bothner
(01 Apr 2022 23:50 UTC)
|
Re: [scheme-reports-wg2] Threads and futures
Ray Dillinger
(02 Apr 2022 00:01 UTC)
|
Re: [scheme-reports-wg2] Threads and futures
Per Bothner
(02 Apr 2022 00:35 UTC)
|
Re: [scheme-reports-wg2] Threads and futures
Linas Vepstas
(10 Apr 2022 23:46 UTC)
|
Re: [scheme-reports-wg2] Threads and futures
Linas Vepstas
(27 Mar 2022 16:54 UTC)
|
On 4/1/22 16:03, Ray Dillinger wrote: > In every header file, you'll see something like > > #ifndef LIB_H > at the top and > > #endif > at the bottom. > > But then the file is #include'd from a hundred places, and each of those > places is #included from three others, and so on..... > > In order to prevent the system from having to read and parse the file > again, leave the above just as it is but also go to all the places in > your program where you say > > #include "lib.h" > > And say instead > > #ifndef LIB_H > #include "lib.h" > #endif From my days as a young gcc hacker, I'm pretty sure gcc does this optimization automatically. Or at least it used to. Other quality compilers probably also do so. -- --Per Bothner xxxxxx@bothner.com http://per.bothner.com/