One note: I personally found the documentation on how to make a class declaration public fairly hard to find. It could be nice to make this clearer.
-Seth On 06/09/2011 01:57 AM, Robert Bradshaw wrote: > I agree. > > On Wed, Jun 8, 2011 at 9:47 AM, <sshan...@stwing.upenn.edu> wrote: >> Yeah, I think just erroring would be perfectly reasonable. >> >> -Seth >> >> Quoting "Greg Ewing" <greg.ew...@canterbury.ac.nz>: >> >>> 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 _______________________________________________ cython-devel mailing list cython-devel@python.org http://mail.python.org/mailman/listinfo/cython-devel
