Most Random fact
- Thread starter AlaynaJ
- Start date
-
Christian Chat is a moderated online Christian community allowing Christians around the world to fellowship with each other in real time chat via webcam, voice, and text, with the Christian Chat app. You can also start or participate in a Bible-based discussion here in the Christian Chat Forums, where members can also share with each other their own videos, pictures, or favorite Christian music.
If you are a Christian and need encouragement and fellowship, we're here for you! If you are not a Christian but interested in knowing more about Jesus our Lord, you're also welcome! Want to know what the Bible says, and how you can apply it to your life? Join us!
To make new Christian friends now around the world, click here to join Christian Chat.
B
Wich is very good. In vb or c#, many people make everything public (easy, cuz always accessible). And then the problems start.
Fact: Did you know that in vb or c# you can even declare every attribute as 'object'-type, wich allows any type? Don't use it, unless really necessary...
Fact: A cessna 152 takes of at a speed of (in general) 55 knots. That is 102 km/h or 63 mph
Fact: Did you know that in vb or c# you can even declare every attribute as 'object'-type, wich allows any type? Don't use it, unless really necessary...
Fact: A cessna 152 takes of at a speed of (in general) 55 knots. That is 102 km/h or 63 mph
B
@ Astrid: Python is indeed different: (I got this from the python docs...)
“Private” instance variables that cannot be accessed except from inside an object, don’t exist in Python. However, there is a convention that is followed by most Python code: a name prefixed with an underscore (e.g. _spam) should be treated as a non-public part of the API (whether it is a function, a method or a data member). It should be considered an implementation detail and subject to change without notice.
Since there is a valid use-case for class-private members (namely to avoid name clashes of names with names defined by subclasses), there is limited support for such a mechanism, called name mangling. Any identifier of the form __spam (at least two leading underscores, at most one trailing underscore) is textually replaced with _classname__spam, where classname is the current class name with leading underscore(s) stripped. This mangling is done without regard to the syntactic position of the identifier, as long as it occurs within the definition of a class.
Note that the mangling rules are designed mostly to avoid accidents; it still is possible to access or modify a variable that is considered private. This can even be useful in special circumstances, such as in the debugger.
Notice that code passed to exec, eval() or execfile() does not consider the classname of the invoking class to be the current class; this is similar to the effect of the global statement, the effect of which is likewise restricted to code that is byte-compiled together. The same restriction applies to getattr(), setattr() and delattr(), as well as when referencing __dict__ directly.
“Private” instance variables that cannot be accessed except from inside an object, don’t exist in Python. However, there is a convention that is followed by most Python code: a name prefixed with an underscore (e.g. _spam) should be treated as a non-public part of the API (whether it is a function, a method or a data member). It should be considered an implementation detail and subject to change without notice.
Since there is a valid use-case for class-private members (namely to avoid name clashes of names with names defined by subclasses), there is limited support for such a mechanism, called name mangling. Any identifier of the form __spam (at least two leading underscores, at most one trailing underscore) is textually replaced with _classname__spam, where classname is the current class name with leading underscore(s) stripped. This mangling is done without regard to the syntactic position of the identifier, as long as it occurs within the definition of a class.
Note that the mangling rules are designed mostly to avoid accidents; it still is possible to access or modify a variable that is considered private. This can even be useful in special circumstances, such as in the debugger.
Notice that code passed to exec, eval() or execfile() does not consider the classname of the invoking class to be the current class; this is similar to the effect of the global statement, the effect of which is likewise restricted to code that is byte-compiled together. The same restriction applies to getattr(), setattr() and delattr(), as well as when referencing __dict__ directly.
G
actually in python everything is a type of object
it is like the VB concept of a variant( eg '12' can be treated as a double or an int or a string using coercion)
BBC Basic was the first language to use coercion that I am aware of
followed by the Sinclair QL
circa 1985
sometimes in vb a particular type does not compile properly but if you just call it an object then it works ok - typical microsoft bugs
i think therefore everything in python is an implicit pointer
for x :0:10:1; (this is a fornext loop)
x goes from 0 to LESS THAN 10 eg 0,1,2,3,4,5,6,7,8,9
r = [for x :0:10:1] gives you [0,1,2,3,4,5,6,7,8,9]
r = [0,1,2,3,4,5,6,7,8,9] very useful that is you get a list holding the results
a variation on this is to take a list of objects
run through this(oldlist) list, applying a condition(filter) so you get another list(newlist) which is a SUBSET of the first one
I havent checked yet but I believe this is a list of pointers to the objects in the original list so if you change one of the objects in the new list it will be reflected in one of the objects in the old list
it is like the VB concept of a variant( eg '12' can be treated as a double or an int or a string using coercion)
BBC Basic was the first language to use coercion that I am aware of
followed by the Sinclair QL
circa 1985
sometimes in vb a particular type does not compile properly but if you just call it an object then it works ok - typical microsoft bugs
i think therefore everything in python is an implicit pointer
for x :0:10:1; (this is a fornext loop)
x goes from 0 to LESS THAN 10 eg 0,1,2,3,4,5,6,7,8,9
r = [for x :0:10:1] gives you [0,1,2,3,4,5,6,7,8,9]
r = [0,1,2,3,4,5,6,7,8,9] very useful that is you get a list holding the results
a variation on this is to take a list of objects
run through this(oldlist) list, applying a condition(filter) so you get another list(newlist) which is a SUBSET of the first one
I havent checked yet but I believe this is a list of pointers to the objects in the original list so if you change one of the objects in the new list it will be reflected in one of the objects in the old list
