Opened 10 years ago
Closed 9 years ago
#1190 closed defect (fixed)
byte-blob: byte-blob->blob or byte-blob-object?
Reported by: | John Foerch | Owned by: | |
---|---|---|---|
Priority: | major | Milestone: | someday |
Component: | unknown | Version: | 4.9.x |
Keywords: | Cc: | ||
Estimated difficulty: |
Description
I need to pass a byte-blob to a foreign function, and found that foreign types scheme-pointer and blob-pointer both gave pointers to the object header rather than the blob contents. Looking into the source of the byte-blob egg, I found byte-blob-object and its alias byte-blob->blob. byte-blob-object is exported by the egg and byte-blob->blob is not exported. I used byte-blob-object to do what I needed to do, however neither of these procedures are mentioned in the documentation on Eggs Unlimited or the chickidee api reference, so I suspect something is unfinished here. Please advise! Thank you.
Change History (4)
comment:1 Changed 10 years ago by
comment:2 Changed 10 years ago by
I've created a new release of byte-blob (1.17) that exports byte-blob->blob and have updated the documentation. Let me know if this works for you.
Replying to retroj:
I need to pass a byte-blob to a foreign function, and found that foreign types scheme-pointer and blob-pointer both gave pointers to the object header rather than the blob contents. Looking into the source of the byte-blob egg, I found byte-blob-object and its alias byte-blob->blob. byte-blob-object is exported by the egg and byte-blob->blob is not exported. I used byte-blob-object to do what I needed to do, however neither of these procedures are mentioned in the documentation on Eggs Unlimited or the chickidee api reference, so I suspect something is unfinished here. Please advise! Thank you.
comment:3 Changed 10 years ago by
Thank you. It looks like endian-blob also needs to be updated now because it uses byte-blob-object.
comment:4 Changed 9 years ago by
Resolution: | → fixed |
---|---|
Status: | new → closed |
byte-blob->blob should have been exported, and the documentation should reflect that. I will fix this shortly.