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

uppercase characters in submodule names #3510

Closed
vicuna opened this issue Mar 3, 2005 · 2 comments
Closed

uppercase characters in submodule names #3510

vicuna opened this issue Mar 3, 2005 · 2 comments
Labels

Comments

@vicuna
Copy link

vicuna commented Mar 3, 2005

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

Bug description

Full_Name: Jeff Henrikson
Version: 3.08.1
OS: Linux
Submission from: rdcsd1.safeco.com (12.144.134.2)

I may be doing something wrong, but there seems to be broken behavior with
submodules having CamelCaps identifiers. (no pun intended!) For example, I can
use the construction ExtLib.List.map but not ExtLib.DynArray.create. Also the
module Foo = Amodule.CamelCaps constructions seems to break. I give some
examples below.

Jeff Henrikson

    Objective Caml version 3.08.1

#directory "+site-lib/extlib";;

#load "extLib.cma";;

module List = ExtLib.List;; (* ok *)

module List :
sig
val init : int -> (int -> 'a) -> 'a list
...
end

module TwoCaps = ExtLib.List;; (* ok *)

module TwoCaps :
sig
val init : int -> (int -> 'a) -> 'a list
...
end

ExtLib.List.map;; (* ok *)

  • : ('a -> 'b) -> 'a list -> 'b list =

ExtLib.DynArray.create;; (* ??? *)

Characters 0-22:
ExtLib.DynArray.create;;
^^^^^^^^^^^^^^^^^^^^^^
Unbound value ExtLib.DynArray.create

module DynArray = ExtLib.DynArray;; (* ??? *)

Characters 18-33:
module DynArray = ExtLib.DynArray;;
^^^^^^^^^^^^^^^
Unbound module ExtLib.DynArray

open ExtLib;; (* ok *)

DynArray.set;; (* ok *)

  • : 'a DynArray.t -> int -> 'a -> unit =

@vicuna
Copy link
Author

vicuna commented Mar 8, 2005

Comment author: administrator

I may be doing something wrong, but there seems to be broken behavior with
submodules having CamelCaps identifiers.

There is no problem with BiCapitalization or TriCapitalizedIdentifiers
either. It's just that ExtLib is structured as follows:

a top-level module ExtLib with submodules List, etc, but not DynArray
a top-level module DynArray
other top-level modules.

So, ExtLib.List is OK, DynArray is OK, but ExtLib.DynArray doesn't exist.

Hope this explaisn the mystery.

  • Xavier Leroy

@vicuna
Copy link
Author

vicuna commented Mar 8, 2005

Comment author: administrator

User got confused by the structure of the ExtLib modules

@vicuna vicuna closed this as completed Mar 8, 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