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

Jump to bottom

value name conflict #4230

Closed
vicuna opened this issue Mar 14, 2007 · 1 comment
Closed

value name conflict #4230

vicuna opened this issue Mar 14, 2007 · 1 comment
Assignees
@damiendoligez
Labels
bug duplicate high-priority stdlib
Milestone
4.03.1

Comments

@vicuna
Copy link

vicuna commented Mar 14, 2007

Original bug ID: 4230
Reporter: Hendrik Tews
Assigned to: @damiendoligez
Status: closed (set by @mshinwell on 2016-12-08T10:55:36Z)
Resolution: duplicate
Priority: high
Severity: minor
Version: 3.09.3
Target version: 4.03.1+dev
Category: runtime system and C interface
Duplicate of: #4164
Related to: #8395 #5254
Monitored by: @hcarty @dbuenzli

Bug description

The caml_ prefix greatly reduced name clashes since 3.08.
Unfortunately, a few global identifiers have not got a caml_
prefix. Most notably "value".

Please add a caml prefix to all identifiers from the C interface.
Especially to "value".

The unrenamed value provokes name clashes in Olmar with "value"
methods in certain classes.
@vicuna
Copy link
Author

vicuna commented Dec 8, 2016

Comment author: @mshinwell

I think this one can be closed since it doesn't provide any new information over and above the other two issues on this subject (#1956 and #4164).

@vicuna vicuna closed this as completed Dec 8, 2016
@vicuna vicuna added this to the 4.03.1 milestone Mar 14, 2019
This was referenced Mar 14, 2019
Closed
Closed
Closed
@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
Assignees

@damiendoligez damiendoligez

Labels
bug duplicate high-priority stdlib
Projects
None yet
Milestone
4.03.1
Development

No branches or pull requests
2 participants
@damiendoligez @vicuna