-
Notifications
You must be signed in to change notification settings - Fork 39
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
[serapi] Add Init
call to the protocol.
#49
Comments
The |
ejgallego
added a commit
that referenced
this issue
Nov 29, 2018
The protocol now supports a call: ``` (NewDoc ((top_name "Module") (iload_path (path_1 ... path_n) (require_libs (require_1 ... require_n)))) ``` where `path_i` is of type ``` Mltop.coq_path = { path_spec: coq_path_spec; recursive: bool; } type coq_path_spec = | VoPath of vo_path_spec | MlPath of string type vo_path_spec = { unix_path : string; coq_path : Names.DirPath.t; implicit : bool; has_ml : add_ml; } ``` and `require_i` is of type: ``` string * string option * bool option ``` where `(module, root, import)` corresponds to `From root Require import module` `iload_path` and `require_libs` are optional, if absent, SerAPI will resort to the defaults. By default, invoking `sertop` will create a document with the standard paths and `Prelude` loaded. To avoid that, use the commit line option `--no_init`. This PR improves a certain number of things, including `compser` and `sercomp` will now create documents with the proper module path cc: #84. This also improves #49 and #59.
ejgallego
added a commit
that referenced
this issue
Nov 29, 2018
The protocol now supports a method: ``` (NewDoc ((top_name "Module") (iload_path (path_1 ... path_n) (require_libs (require_1 ... require_n)))) ``` where `path_i` is of type ``` Mltop.coq_path = { path_spec: coq_path_spec; recursive: bool; } type coq_path_spec = | VoPath of vo_path_spec | MlPath of string type vo_path_spec = { unix_path : string; coq_path : Names.DirPath.t; implicit : bool; has_ml : add_ml; } ``` and `require_i` is of type: ``` string * string option * bool option ``` where `(module, root, import)` corresponds to `From root Require import module` `iload_path` and `require_libs` are optional, if absent, SerAPI will resort to the defaults. By default, invoking `sertop` will create a document with the standard paths and `Prelude` loaded. To avoid that, use the commit line option `--no_init`. This PR improves a certain number of things, including `compser` and `sercomp` will now create documents with the proper module path cc: #84. This also improves #49 and #59.
ejgallego
added a commit
that referenced
this issue
Nov 29, 2018
The protocol now supports a method: ``` (NewDoc ((top_name "Module") (iload_path (path_1 ... path_n) (require_libs (require_1 ... require_n)))) ``` where `path_i` is of type ``` Mltop.coq_path = { path_spec: coq_path_spec; recursive: bool; } type coq_path_spec = | VoPath of vo_path_spec | MlPath of string type vo_path_spec = { unix_path : string; coq_path : Names.DirPath.t; implicit : bool; has_ml : add_ml; } ``` and `require_i` is of type: ``` string * string option * bool option ``` where `(module, root, import)` corresponds to `From root Require import module` `iload_path` and `require_libs` are optional, if absent, SerAPI will resort to the defaults. By default, invoking `sertop` will create a document with the standard paths and `Prelude` loaded. To avoid that, use the commit line option `--no_init`. **Important** in practice the user still can only use this option to create one single document using `NewDoc`, as the protocol doesn't yet include per-document addressing. This PR improves a certain number of things, including `compser` and `sercomp` will now create documents with the proper module path cc: #84. This also improves #49 and #59.
ejgallego
added a commit
that referenced
this issue
Feb 14, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
As of today, SerAPI creates a new document by default, with standard loadpaths, libraries, etc...
This can be overridden to some point using cmdline parameters, but we would like to have proper protocol support for that, as well as for document ids and for output formats. Thus, the init call should support as parameters:
Pending
Fixed by #69
Add
the first sentence to #14]The text was updated successfully, but these errors were encountered: