Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.python > #12360
| From | Terry Reedy <tjreedy@udel.edu> |
|---|---|
| Subject | Re: Why PyImport_ExecCodeModule takes char*? |
| Date | 2011-08-28 20:02 -0400 |
| References | <mailman.447.1314375134.27778.python-list@python.org> <jkhl579a7k66v3n3pe1pacq7j0st7nsnq4@4ax.com> |
| Newsgroups | comp.lang.python |
| Message-ID | <mailman.521.1314576217.27778.python-list@python.org> (permalink) |
On 8/28/2011 6:52 PM, Tim Roberts wrote: > Mateusz Loskot<mateusz@loskot.net> wrote: >> >> I'm wondering, why PyImport_ExecCodeModule function takes char* >> instead of const char*? > > My guess is "history". I believe some const tags have been added over the last few years. Another factory than mere history for some things is portability across platforms and the main compilers. -- Terry Jan Reedy
Back to comp.lang.python | Previous | Next — Previous in thread | Find similar | Unroll thread
Why PyImport_ExecCodeModule takes char*? Mateusz Loskot <mateusz@loskot.net> - 2011-08-26 16:40 +0100
Re: Why PyImport_ExecCodeModule takes char*? Tim Roberts <timr@probo.com> - 2011-08-28 15:52 -0700
Re: Why PyImport_ExecCodeModule takes char*? Terry Reedy <tjreedy@udel.edu> - 2011-08-28 20:02 -0400
csiph-web