A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from https://mail.python.org/pipermail/python-dev/2002-December/031073.html below:

[Python-checkins] python/dist/src/Include co mpile.h,2.38,2.39 parsetok.h,2.19,2.20 pyerrors.h,2.63,2.64 pythonrun.h,2 .55,2.56 symtable.h,2.10,2.11

[Python-Dev] Re: [Python-checkins] python/dist/src/Include co mpile.h,2.38,2.39 parsetok.h,2.19,2.20 pyerrors.h,2.63,2.64 pythonrun.h,2 .55,2.56 symtable.h,2.10,2.11Martin v. Löwis Martin v. Löwis
Thu, 12 Dec 2002 10:06:41 +0100
> > Well, it depends how you define "user".  When working on win32all, I
am a
> > developer.  However, when knocking up a simple little extension for
Python
> > for some silly reason, I feel more like a user.
>
> It is definitely useful for the developer and that's what
> I wanted to hint at: the user doesn't notice any change by
> introducing "const".

I see that my terminology was confusing: user: software author who uses
the Python header files. developer: software author who writes them.
Strictly speaking, computer users never "use" Python: they always use
some Python application. So the Python "users" are always software
authors. Of those, only the authors who write C extensions will notice a
change. Sorry for the confusion.

> I'm all for using "const" in new APIs too (I've added it to most
> Unicode APIs for that reason), what worries me is that existing APIs
> get converted.

No need to worry. Nothing can break because of that.

Regards,
Martin




RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4