SDA SE Wiki

Software Engineering for Smart Data Analytics & Smart Data Analytics for Software Engineering

User Tools

Site Tools


Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Next revision
Previous revision
research:pdt:docs:entry_point [2018/04/15 13:50]
127.0.0.1 external edit
research:pdt:docs:entry_point [2018/05/09 01:59] (current)
Line 10: Line 10:
   * File will be highlighted with an icon (which will be saved persistently in the workspace, not depending on the current Prolog process and still available after a restart of eclipse).   * File will be highlighted with an icon (which will be saved persistently in the workspace, not depending on the current Prolog process and still available after a restart of eclipse).
   * If the file is consulted in your current process, the fact "//​pdt_entry_point(Filename)//"​ will be added. This might be useful for dead code analysis (e.g. files which aren't loaded from an entry point are dead code).   * If the file is consulted in your current process, the fact "//​pdt_entry_point(Filename)//"​ will be added. This might be useful for dead code analysis (e.g. files which aren't loaded from an entry point are dead code).
 +  * Last but no least, when you restart a Prolog process the PDT will by default reconsult entry point files. This saves you the small trouble of doing it yourself and the bigger trouble of forgetting to do it and wondering why things don't work anymore. You can alternatively choose to restart without reloading entry points or restart and relaoding all loaded files. The last option is to be used with caution, keeping in mind that one of the recently added files that are not yet consulted from the entry point might be the problem why your Prolog process crashed or looped infinitely. The rule of thumb is to consult only reasonably well tested code from the entry points. ​
  
  
research/pdt/docs/entry_point.txt · Last modified: 2018/05/09 01:59 (external edit)

SEWiki, © 2019