Re: [Cython] Header file bug
Seth Shannin wrote: I would still make the case that currently something is a bit off in that the header file tries to use something which it has no information about Yes, I agree that it could do with improvement. I'm not sure that automatically putting the struct declaration in the header is the best idea, though, since with mangled names it's hard to do anything with it from external C code (that's why you're required to manually supply type and object struct names). Maybe it should just be an error to make a declaration public if it uses something that's non-public? -- Greg ___ cython-devel mailing list cython-devel@python.org http://mail.python.org/mailman/listinfo/cython-devel
Re: [Cython] Header file bug
Yeah, I think just erroring would be perfectly reasonable. -Seth Quoting "Greg Ewing" : Seth Shannin wrote: I would still make the case that currently something is a bit off in that the header file tries to use something which it has no information about Yes, I agree that it could do with improvement. I'm not sure that automatically putting the struct declaration in the header is the best idea, though, since with mangled names it's hard to do anything with it from external C code (that's why you're required to manually supply type and object struct names). Maybe it should just be an error to make a declaration public if it uses something that's non-public? -- Greg ___ cython-devel mailing list cython-devel@python.org http://mail.python.org/mailman/listinfo/cython-devel ___ cython-devel mailing list cython-devel@python.org http://mail.python.org/mailman/listinfo/cython-devel
Re: [Cython] Header file bug
I agree. On Wed, Jun 8, 2011 at 9:47 AM, wrote: > Yeah, I think just erroring would be perfectly reasonable. > > -Seth > > Quoting "Greg Ewing" : > >> Seth Shannin wrote: >>> >>> I would still make the case that currently >>> something is a bit off in that the header file tries to use something >>> which it has no information about >> >> Yes, I agree that it could do with improvement. I'm not sure >> that automatically putting the struct declaration in the >> header is the best idea, though, since with mangled names it's >> hard to do anything with it from external C code (that's why >> you're required to manually supply type and object struct names). >> >> Maybe it should just be an error to make a declaration public >> if it uses something that's non-public? >> >> -- >> Greg >> ___ >> cython-devel mailing list >> cython-devel@python.org >> http://mail.python.org/mailman/listinfo/cython-devel >> > > > ___ > cython-devel mailing list > cython-devel@python.org > http://mail.python.org/mailman/listinfo/cython-devel > ___ cython-devel mailing list cython-devel@python.org http://mail.python.org/mailman/listinfo/cython-devel
