Tweak OC_Python* classes to support secure encoding for where possible

Issue #180 closed
Ronald Oussoren repo owner created an issue

The OC_Python* classes don't support secure encoding for general Python objects, but can do so for most builtin Python types.

It should be possible to actually support this by splitting all classes into two: one used for builtin python classes that supports secure coding, and one for other classes that doesn't.

Something like:

@interface OC_PythonArray -> Any python sequence, doesn't support secure coding

@interface OC_PythonBuiltinArray -> Python "list" and "tuple" (exact classes), does support secure coding

Comments (3)

  1. Ronald Oussoren reporter

    Introduce secureCoding support

    This introduces secure coding support for a number of classes, see #180 and #251.

    This patch is not yet complete, for some reason using OC_BuiltinPythonNumber causes test failures in the NSCoding tests.

    → <<cset 66453e390b64>>

  2. Log in to comment