Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.python > #37222 > unrolled thread
| Started by | Steve Simmons <square.steve@gmail.com> |
|---|---|
| First post | 2013-01-21 16:52 +0000 |
| Last post | 2013-01-21 16:52 +0000 |
| Articles | 1 — 1 participant |
Back to article view | Back to comp.lang.python
This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by
below is the oldest one visible, not the original post.
Re: handling return codes from CTYPES Steve Simmons <square.steve@gmail.com> - 2013-01-21 16:52 +0000
| From | Steve Simmons <square.steve@gmail.com> |
|---|---|
| Date | 2013-01-21 16:52 +0000 |
| Subject | Re: handling return codes from CTYPES |
| Message-ID | <mailman.761.1358797637.2939.python-list@python.org> |
Mike,
Thanks for your response - I was puzzled by one part of it though...
On 21/01/2013 15:14, Mike C. Fletcher wrote:
> That's because you've just discarded the object you created
I (mis?)understood from the ctypes documentation that '>>> initResult =
c_short(0)' would result in the creation of a ctypes 'short' called
initResult and that this object would be mutable. On that basis, I
expected the following statement '>>> initResult = initScanLib( ... )'
would assign the result of the call to initResult.
So, I can understand that I am not using the correct approach but I
don't understand how I discarded the object I created. Can you clarify
please?
Steve
Back to top | Article view | comp.lang.python
csiph-web