| … | |
… | |
| 299 | The design goals for this mechanism were to be simple to use, very |
299 | The design goals for this mechanism were to be simple to use, very |
| 300 | efficient when not needed, low code and data size overhead and broad |
300 | efficient when not needed, low code and data size overhead and broad |
| 301 | applicability. |
301 | applicability. |
| 302 | |
302 | |
| 303 | =back |
303 | =back |
|
|
304 | |
|
|
305 | |
|
|
306 | =head1 DISABLING PERL MULTICORE AT COMPILE TIME |
|
|
307 | |
|
|
308 | You can disable the complete perl multicore API by defining the |
|
|
309 | symbol C<PERL_MULTICORE_DISABLE> to C<1> (e.g. by specifying |
|
|
310 | F<-DPERL_MULTICORE_DISABLE> as compiler argument). |
|
|
311 | |
|
|
312 | This will leave no traces of the API in the compiled code, suitable |
|
|
313 | "empty" C<perl_release> and C<perl_acquire> definitions will be provided. |
|
|
314 | |
|
|
315 | This could be added to perl's C<CPPFLAGS> when configuring perl on |
|
|
316 | platforms that do not support threading at all for example. |
|
|
317 | |
| 304 | |
318 | |
| 305 | =head1 AUTHOR |
319 | =head1 AUTHOR |
| 306 | |
320 | |
| 307 | Marc A. Lehmann <perlmulticore@schmorp.de> |
321 | Marc A. Lehmann <perlmulticore@schmorp.de> |
| 308 | http://perlmulticore.schmorp.de/ |
322 | http://perlmulticore.schmorp.de/ |
