Ticket #320 (new defect)

Opened 5 years ago

Last modified 3 years ago

Type checking when casting objects to pointers

Reported by: dagss Owned by: somebody
Priority: minor Milestone: wishlist
Component: Type Analysis Keywords:

Description (last modified by scoder) (diff)

a) There's currently a lot of different PyObject declarations floating around in Cython/Includes. This could be fixed by centralizing them. [DONE]

b) However, currently it is possible to do <AnyStruct*>pyobject. This is probably a bit too lenient -- one would wish to require <AnyStruct*><void*>pyobject; while still allowing <PyObject*>pyobject. This could speak in favor of making PyObject a builtin.

Change History

Changed 5 years ago by scoder

  • component changed from Parsing to Type Analysis
  • description modified (diff)
  • milestone changed from wishlist to 0.12

Targeting this to 0.12 as it's really annoying. There should be a builtin "PyObject?" type that's simply known without any cimports.

Changed 4 years ago by scoder

  • milestone changed from 0.12 to 0.13

This has not been decided yet. The cleanup in Cython/Includes/ lifts the weight from this problem. Retargeting to 0.13.

Changed 4 years ago by robertwb

  • milestone changed from 0.13 to 0.13.1

Changed 3 years ago by robertwb

  • priority changed from major to minor
  • milestone changed from 0.14 to wishlist

Changed 3 years ago by scoder

  • description modified (diff)
  • summary changed from Canonical PyObject to Type checking when casting objects to pointers

Changed subject to represent the left-over parts of this bug.

Note: See TracTickets for help on using tickets.