Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Enhance "output_value: abstract value" message #2368

Closed
vicuna opened this issue Mar 22, 2004 · 2 comments
Closed

Enhance "output_value: abstract value" message #2368

vicuna opened this issue Mar 22, 2004 · 2 comments

Comments

@vicuna
Copy link

vicuna commented Mar 22, 2004

Original bug ID: 2368
Reporter: administrator
Status: closed
Resolution: fixed
Priority: normal
Severity: feature
Category: ~DO NOT USE (was: OCaml general)

Bug description

Full_Name: John Gerard Malecki
Version: 3.07
OS: linux & solaris
Submission from: 192-149-105-50.artisan.com (192.149.105.50)

The call

extern_invalid_argument("output_value: abstract value");

appears 3 times in extern_rec (in byterun/extern.c). Would it be possible to
make a tiny change to the message for each location to be able to distinguish an
Abstract_tag from a Custom_tag and an object allocated outside the heap?

-thanks

@vicuna
Copy link
Author

vicuna commented Apr 13, 2004

Comment author: administrator

Hello,

Full_Name: John Gerard Malecki

extern_invalid_argument("output_value: abstract value");

appears 3 times in extern_rec (in byterun/extern.c). Would it be possible to
make a tiny change to the message for each location to be able to distinguish
an
Abstract_tag from a Custom_tag and an object allocated outside the heap?

Thanks for your suggestion. I have implemented it in the CVS version.

-- Damien

@vicuna
Copy link
Author

vicuna commented Apr 13, 2004

Comment author: administrator

done DD 2004-04-14

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant