Message 65940 - Python tracker

➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author	ndbecker
Recipients	loewis, ndbecker
Date	2008-04-28.22:35:36
SpamBayes Score	0.015414673
Marked as misclassified	No
Message-id	<200804281835.26548.ndbecker2@gmail.com>
In-reply-to	<48164B99.3080406@v.loewis.de>

Content
On Monday 28 April 2008, Martin v. Löwis wrote: > Martin v. Löwis <martin@v.loewis.de> added the comment: > > IIUC, current ioctl is not capable of handling arbitrary argument > > types. > > Can you please be a bit more explicit? What limitation do you see in > fcntl.ioctl, and how does this fragment overcome the limitation? > AFAICT, they do exactly the same thing. > In the example I gave, the ioctl passes a structure: class eos_dl_args_t (Structure): _fields_ = [("length", c_ulong), ("data", c_void_p)] AFAIK, there is no way to do that with fcntl.ioctl, is there?

On Monday 28 April 2008, Martin v. Löwis wrote:
> Martin v. Löwis <martin@v.loewis.de> added the comment:
> > IIUC, current ioctl is not capable of handling arbitrary argument
> > types.
>
> Can you please be a bit more explicit? What limitation do you see in
> fcntl.ioctl, and how does this fragment overcome the limitation?
> AFAICT, they do exactly the same thing.
>

In the example I gave, the ioctl passes a structure:

class eos_dl_args_t (Structure):
    _fields_ = [("length", c_ulong),
                ("data", c_void_p)]

AFAIK, there is no way to do that with fcntl.ioctl, is there?

History
Date	User	Action	Args
2008-04-28 22:35:37	ndbecker	set	spambayes_score: 0.0154147 -> 0.015414673 recipients: + ndbecker, loewis
2008-04-28 22:35:36	ndbecker	link	issue2712 messages
2008-04-28 22:35:36	ndbecker	create