Changes between Version 5 and Version 6 of ErlangShellInterface
- Timestamp:
- Apr 17, 2012, 8:41:44 AM (13 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
ErlangShellInterface
v5 v6 40 40 }}} 41 41 42 You can also specify build parameters, but this feature is mostly applied through the development, so please find the module documentation for the details. Note that this build function tries to compile the C++ files as well, if they have not been compiled yet. If you want to prevent the C++ compilation, you can use the {{{no_nif}}} build parameter.42 You can also specify build parameters, but this feature is mostly applied through the development, so please find the module documentation for the details. Note that this build function tries to compile the nif graph representation as well, if these have not been compiled yet. If you want to prevent this, you can use the {{{no_nif}}} build parameter. 43 43 44 44 == Managing files == … … 50 50 If you specify a directory instead of a regular filename, then it will be recursively 51 51 traversed. You may just as well give a list of atoms or strings to add more files 52 at once. All of the following example commands would add the same le:52 at once. All of the following example commands would add the same file: 53 53 54 54 {{{ … … 62 62 The module displays the progression of loading. 63 63 Removing files from the database is similarly easy and also recursive, except 64 for one difference. As the system by the time you want to remove a module must 65 know the exact location of the said, you need not restrict yourself to dropping a 66 module relative to the current directory, but must in exchange use real module 64 for one difference. You need not restrict yourself to dropping a 65 module relative to the current directory, but in exchange you must use real module 67 66 names that do not contain path delimiters. The following will equally work: 68 67 … … 143 142 }}} 144 143 145 Loading BEAM files.Usually, Erlang source files (having the extension144 Usually, Erlang source files (having the extension 146 145 .erl) are loaded into !RefactorErl. In addition, !RefactorErl is also capable of 147 146 loading compiled .beam files. … … 160 159 [[RefactoringSteps|refactoring functionalities]]. 161 160 There is another way to call a transormation. This way let the user to 162 choose: user want to specify all of arguments or not. There are lots of cases161 choose: user wants to specify all of arguments or not. There are lots of cases 163 162 when the user can not specify all of the required arguments. In this case the 164 163 tool can help the user with interactions. The tool ask questions and the user 165 164 has to answer it to specify the missing arguments. The interactions also work if 166 there is some problemwith the given arguments.165 there are problems with the given arguments. 167 166 168 167 == Manipulating the graph == … … 188 187 }}} 189 188 190 If you use NIF , then it is little different:[[BR]]189 If you use NIF graph database, then it is little different:[[BR]] 191 190 You can create backups with '''ri:backup/0''' or '''ri:backup/1''' and you can load 192 191 these backups with '''ri:restore/1'''. … … 209 208 }}} 210 209 211 The representation can be ltered:210 The representation can be altered: 212 211 213 212 {{{ … … 258 257 argument. The following arguments are currently recognized:\\ 259 258 * '''{out,!FileName}''': write the textual output of a query to a file.\\ 260 * '''linenum''': prepends match sites with le and line number information.\\259 * '''linenum''': prepends match sites with file and line number information.\\ 261 260 similar to '''grep -n'''. 262 261 The following example outputs all defined functions with line numbers to a
