Exporting the canonical null value for pack/unpack Vasilij Schneidermann (20 Nov 2020 11:56 UTC)
Re: Exporting the canonical null value for pack/unpack Amirouche Boubekki (20 Nov 2020 16:20 UTC)
Re: Exporting the canonical null value for pack/unpack John Cowan (20 Nov 2020 16:22 UTC)
Re: Exporting the canonical null value for pack/unpack Vasilij Schneidermann (20 Nov 2020 16:33 UTC)
Re: Exporting the canonical null value for pack/unpack Vasilij Schneidermann (30 Nov 2020 11:30 UTC)
Re: Exporting the canonical null value for pack/unpack Amirouche Boubekki (30 Nov 2020 12:12 UTC)
Re: Exporting the canonical null value for pack/unpack John Cowan (30 Nov 2020 16:17 UTC)
Re: Exporting the canonical null value for pack/unpack Amirouche Boubekki (30 Nov 2020 16:19 UTC)

Re: Exporting the canonical null value for pack/unpack Amirouche Boubekki 30 Nov 2020 16:19 UTC

Le lun. 30 nov. 2020 à 17:17, John Cowan <xxxxxx@ccil.org> a écrit :
>
>
>
> On Mon, Nov 30, 2020 at 6:30 AM Vasilij Schneidermann <xxxxxx@vasilij.de> wrote:
>
>>
>> I've looked at this now and discovered that it must be a procedure as
>> the null value is unique to the engine
>
>
> Why is this?  I'd think the framework should convert the engine-specific null into a universal null.

It really depends on the pack and unpack procedure. Since `pack` and
`unpack` should be only accessed via `engine-pack` and
`engine-unpack`, it makes sense to also have `engine-null`.