[Martin v. Loewis] > Brett Cannon <bac@OCF.Berkeley.EDU> writes: > > > > where fields is a list of (name,doc) tuples. The resulting thing would > > > be similar to os.stat_result: you need to call it with the mandatory > > ^^^^^^^ > > You meant "can", right, Martin? > > Probably an English-language issue: If you call it, the mandatory > fields must be present as positional arguments (i.e. you can't call it > and omit mandatory fields, or pass them as keyword arguments). > Yeah, that is what I thought you meant. > > I think the idea is good if you can get it to tie directly into C code. > > That would get a +1 from me. If not, then +0. > > What means to "tie into C code" here? > Somehow being able to use this setup with C extensions; possibly as a direct hook into actual C structs with minimal Python objection conversion fuss. So setting values in the structseq could somehow alter the underlying C struct directly. That is what I took away from one of your earlier comments. -Brett
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4