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

-I et toplevel #2479

Closed
vicuna opened this issue Jun 9, 2000 · 1 comment
Closed

-I et toplevel #2479

vicuna opened this issue Jun 9, 2000 · 1 comment
Labels

Comments

@vicuna
Copy link

vicuna commented Jun 9, 2000

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

Bug description

~ $ ocamlmktop -I /usr/local/findlib/site-lib/pcre -o mytop pcre.cma
~ $ ./mytop
Objective Caml version 3.00

Pcre.exec;;

Unbound value Pcre.exec

~ $ ./mytop -I /usr/local/findlib/site-lib/pcre
Objective Caml version 3.00

Pcre.exec;;

  • : ?iflags:Pcre.irflag ->
    ?flags:Pcre.rflag list ->
    ?rex:Pcre.regexp -> ?pat:string -> ?pos:int -> string ->
    Pcre.substrings
    =

Quand on compile un toplevel avec l'option -I pour qu'il trouve un certain
package, il faut l'option -I également pour l'exécuter, alors qu'elle
devrait, à mon avis, ne pas être nécessaire, tant que ça reste dans le même
répertoire. Est-ce voulu ?

~ $ ocamlmktop -I /usr/local/findlib/site-lib/pcre -o mytop pcre.cma
dynlink.cma
~ $ ./mytop -I /usr/local/findlib/site-lib/pcre
Objective Caml version 3.00

Pcre.exec;;

Unbound value Pcre.exec

~ $ ./mytop
Objective Caml version 3.00

#directory "/usr/local/findlib/site-lib/pcre";;

Pcre.exec;;

  • : ?iflags:Pcre.irflag ->
    ?flags:Pcre.rflag list ->
    ?rex:Pcre.regexp -> ?pat:string -> ?pos:int -> string ->
    Pcre.substrings
    =

Dans un même registre, si on compile un toplevel avec le package dynlink,
il se met subitement à ignorer l'option -I. Ceci me semble être clairement
un bug.

@vicuna
Copy link
Author

vicuna commented Feb 27, 2001

Comment author: administrator

ocamlmktop -I: no way to do otherwise. (Can't "remember" -I options in a custom
toplevel.)
dynlink and toplevel: cause duplication of internal modules, in particular
Config.load_path. No way to get it right with the current flat module
namespace.

@vicuna vicuna closed this as completed Jun 25, 2001
@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