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

callback.h: caml_named_value should consume a const string #3396

Closed
vicuna opened this issue Dec 22, 2004 · 1 comment
Closed

callback.h: caml_named_value should consume a const string #3396

vicuna opened this issue Dec 22, 2004 · 1 comment
Labels
duplicate feature-wish

Comments

@vicuna
Copy link

vicuna commented Dec 22, 2004

Original bug ID: 3396
Reporter: administrator
Status: closed (set by @damiendoligez on 2006-09-11T12:13:43Z)
Resolution: fixed
Priority: normal
Severity: feature
Category: ~DO NOT USE (was: OCaml general)
Duplicate of: #3178

Bug description

Full_Name: Christoph Bauer
Version: 3.08.2
OS: Windows, Linux
Submission from: 213.68.136.226 (213.68.136.226)

This is not a (serious) bug, but the definition of caml_named_value
produces a warning a C-function of mine.

callback.h
< CAMLextern value * caml_named_value (char * name);

CAMLextern value * caml_named_value (char const * name);

In consequence in callback.c, this has to be done:
callback.c
< static unsigned int hash_value_name(char *name)

static unsigned int hash_value_name(char const*name)

Thank you,
Christoph Bauer
@vicuna
Copy link
Author

vicuna commented Sep 11, 2006

Comment author: @damiendoligez

done for 3.10

@vicuna vicuna closed this as completed Sep 11, 2006
@vicuna vicuna mentioned this issue Sep 11, 2006
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
duplicate feature-wish
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@vicuna