Reflecting latest answers to global and "proposals"
Ad hominem.
There is a slogan: "There are always two persons involved"
This I dont want talk about. I dont go into such a discussion.
It seems more a problem of misinterpretations.
Proofs.
Not really proofs. I meant more or less proofs. Proo
Some notes to the "global"-keyword and the other proposals.
It has been proposed to have these six enhancements
1. optional keyword "global"
2. switch statement
3. less restrictive indentation
4. universal scope
5. goto label
6- "include" script statement
with following proofs uncommented:
Before reflecting latest answers
a short absolute last statement about that matter:
Differ: globals (traditional, sharing vars app wide, NOT meant)
globals (module vars outside functions, meant here at least when I
mention this term)
global (the keyword used inside f
Now I want reflecting the latest answers:
I think mostly everything is said.
Maybe you skip directly to my conclusion on the end.
--
Nevertheless I want grasp some points out
where I think I could give a respective answer:
"You are shifting declaration from one to another place"
I would n
Before responding (later) I have to add something additional first:
Cause of complaints and while still exists and again and again:
When I mentioned maybe OO first than for also this reason
cause Python is a powerful language and supports procedural
and OO features and many more.
And cause a
Now I want reflecting the latest answers:
I have the position of a high-level view
(cause of lack of Python knowledge internals and compiler stuff,
but also cause I think a language should be as far as possible
user-friendly without knowing too much internals, and yes
clearly cause of knowin
Before responding (later) I have to add something additional first:
About the OO comments
(Note again for this 2nd main topic of this thread:
the term "globals" - it is meant only as the vars of a module outside
functions
and not sharing vars throughout the app
th
Reflecting the answers I want to add following first:
I should have better started a new thread.
But now it is here, I want just clarify something before
I move on (later) with repsonding.
I think this has lead to some confusing.
There are now two main topics in this thread.
First topic:
Reflecting the answers I want to add following:
Considering class usage is something I thought about
but is not the way I want use Python so far.
If so, I could stay on oo-scripting languages as well.
It is the good idea of Python about modules which are singletons
and therefore have already i
And to clarify: I have not spoken about sharing constants global (spanning
over modules), where the solution provided here using imports is the solution.
I have spoken from module vars which are named or are "globals" and its
read/write access constraints inside module functions. So even the n
I agree with Skybuck Flying.
I am aware if a var is a module function var or a module global var.
If I want read or write a global var.
Using the keyword global inside each(!) function only
to mark the global var writeable in each of the functions
is really an over-regulation and very annoying f
11 matches
Mail list logo
