On Friday, May 10, 2013 12:02:08 AM UTC+5:30, Nobody wrote:
This line should be:
spiro_to_bezier_strict ( src, len ( src ), byref(bc) )
Without the byref(...), it will try to pass a copy of the structure rather
than passing a pointer to it.
Wow silly silly mistake of mine, passing an object
Hello. I am running Kubuntu Raring with Python 3.3.1. (I mostly don't myself
use Py2.)
I have the below C program spiro.c (obviously a simplified testcase) which I
compile to a sharedlib using clang -fPIC -shared -o libspiro.so spiro.c, sudo
cp to /usr/lib and am trying to call from a Python
I like this one for some reason. Just the using self would save hella
typing in a lot of classes. I would favor a convention with leading dots
to disambiguate from other variables. This wouldn't conflict with, say,
floats, because variable names can't begin with a number.
Excellent. Now we
On Apr 14, 5:06 pm, Duncan Booth [EMAIL PROTECTED] wrote:
I can't see how it is going to save you any typing over what you can
already do.
The suggested example:
The suggested example is only a small case. I realize that the main
usage would be when there are a lot of repetitive usages when
Personally, I'd never use it.
You are free to avoid using it of course. :)
In more complex modules, when you are
looking for, e. g., self.myVar and anotherObject.myVar,
this using statement decreases readability and maintainability
(in full text searching). IMHO.
Why? Just search for self
Languages like Perl and VB need a strict mode because they will
auto-vivify variable for you. I.e. they will bring variables to life
with defined or undefined values if you use them in a l-value (left hand
side of an assignment) without having declared them prior. If you do
that in Python
On Apr 14, 4:01 pm, Martin v. Löwis [EMAIL PROTECTED] wrote:
This one is not sane. It's not possible to change the indexing of
objects on a per-module basis, as objects may cross module boundaries.
I do not request for this to be changed per-module. Once I say
something like:
from __future__
Modules are parsed when they are imported. And some modules are already
imported before your module is imported because they are built-in or
loaded to be able to import your module in the first place. And what
about modules that are written in C?
OK fine. It is clear that this feature must
You already can emulate the using statement like this:
You can emulate only assignments like this. How would you emulate
function calls, like the ones in my example?
--
http://mail.python.org/mailman/listinfo/python-list
On Apr 14, 7:20 pm, Clement [EMAIL PROTECTED] wrote:
Is there any command like Option Explicit[In visual basic].
We have been discussing that over the past few hours. Please see the
thread:
Python Feature Request: Explicit Variable Declarations.
--
On Apr 15, 2:01 am, Bjoern Schliessmann usenet-
[EMAIL PROTECTED] wrote:
self.myVar -- something lost, something gained, IMHO.
So, the gain is the loss of something different? If you say so.
My mistake - I should have said no pain, no gain.
IMHO, the ability to find something quickly
On Apr 14, 3:56 pm, Martin v. Löwis [EMAIL PROTECTED] wrote:
for prior discussion. The request is sane, but is also incomplete: there
is no syntax suggested for the actual declarations of local variables,
and no discussion whether this is meant to apply to local variables
only, or also to
12 matches
Mail list logo
