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:29 UTC)
|
Re: Exporting the canonical null value for pack/unpack
Amirouche Boubekki
(30 Nov 2020 12:11 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 Vasilij Schneidermann 30 Nov 2020 11:29 UTC
Hello again, > I think when an immutable object is exported from a library, it must > be done as a procedure like eof-object. > So in this case, the procedure `engine-null` seems to do the job? I've looked at this now and discovered that it must be a procedure as the null value is unique to the engine and should ideally have a (engine-null engine) function signature. However that would mean extending the engine record accordingly and adjusting the documentation in a few more places. Is that acceptable for you?