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

Representation of objects (manual wrong) #3458

Closed
vicuna opened this issue Feb 6, 2005 · 1 comment
Closed

Representation of objects (manual wrong) #3458

vicuna opened this issue Feb 6, 2005 · 1 comment
Labels

Comments

@vicuna
Copy link

vicuna commented Feb 6, 2005

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

Bug description

The manual says:

18.3.5 	Objects

Objects are represented as zero-tagged blocks. The first field of the
block refers to the object class and associated method suite, in a
format that cannot easily be exploited from C. The remaining fields of
the object contain the values of the instance variables of the
object. Instance variables are stored in the order in which they
appear in the class definition (taking inherited classes into
account).

But this appears not to be quite the case. Firstly, objects are
tagged with Object_tag (248). Secondly it seems like the unique
object ID (Oo.id) is stored in the second field, with the instance
variables coming in the third and subsequent fields. (I suppose we
can say that all objects inherit from an implied superclass containing
an ID field, but it would be nice for the documentation to be clearer
on this).

Rich.

--
Richard Jones, CTO Merjis Ltd.
Merjis - web marketing and technology - http://merjis.com
Team Notepad - intranets and extranets for business - http://team-notepad.com

@vicuna
Copy link
Author

vicuna commented Jul 15, 2005

Comment author: administrator

Fixed as indicated by JG (2005-07-15)

@vicuna vicuna closed this as completed Jul 15, 2005
@vicuna vicuna added the bug label Mar 19, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant