You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Original bug ID: 3432 Reporter: administrator Status: closed Resolution: fixed Priority: normal Severity: minor Category: ~DO NOT USE (was: OCaml general)
In file "win32caml/startocaml.c", line 144-150. It seems that the program is
expected to find the interpreter by the key "InterpreterPath" or asking the
user.
If there is no key named "InterpreterPath" in the registry yet, these codes
will work well. But if the key already exists and is set to a wrong value, the
program will show the error message("Incorrect path for ocaml.exe")
repeatedly(without asking the user for a correct interpreter path).
I changed the codes like this:
Original bug ID: 3432
Reporter: administrator
Status: closed
Resolution: fixed
Priority: normal
Severity: minor
Category: ~DO NOT USE (was: OCaml general)
Bug description
Full_Name: Wei Wong
Version: 3.08.2
OS: win2000
Submission from: 218.94.65.252 (218.94.65.252)
In file "win32caml/startocaml.c", line 144-150. It seems that the program is
expected to find the interpreter by the key "InterpreterPath" or asking the
user.
If there is no key named "InterpreterPath" in the registry yet, these codes
will work well. But if the key already exists and is set to a wrong value, the
program will show the error message("Incorrect path for ocaml.exe")
repeatedly(without asking the user for a correct interpreter path).
I changed the codes like this:
// ==========================================================
// ...
if ((!ReadRegistry(HKEY_CURRENT_USER,
"Software", "Objective Caml",
"InterpreterPath", path) || path[0] == 0)
&&
(!ReadRegistry(HKEY_LOCAL_MACHINE,
"Software", "Objective Caml",
"InterpreterPath", path) || path[0] == 0)) {
// ...
// ==========================================================
Besides, I'm sorry for my poor English. :P
The text was updated successfully, but these errors were encountered: