This repository has been archived by the owner on Apr 2, 2024. It is now read-only.
Assume default PROPATH for include files in current source directory #50
Comments
|
Done in the next version, the relative path will also work correctly |
jcaillon
added a commit
that referenced
this issue
Jan 1, 2016
- #50: Assume default PROPATH for include files is the current source directory - #54: wait the minimum number of char required even after a ":" - #49: major improvement of tables/temp-tables usage detection; the code explorer now allows you to answers those questions: * which tables / temp-tables are used in the program? * do i call database tables without using a buffer? * do i call a database table without specifying its database? - #24: reduced loading time to a flat amount - New option to automatically hide the code/file explorer when switching to non progress document - Complete revamp of the "Options" menu **Corrected issues :** - #56: now prevents the tooltip from cropping the name of the hovered word - #58: in strings, only functions trigger the tooltip - #57: fixed with the last commit - #48: fixed a bug that would sometime cause a glitch on the text display in scintilla
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Hi,
Can you make 3P assume the default PROPATH is ".", where "." means the current source directory, even if there is no customized PROPATH?
This will allow 3P to parse include files contained in the same directory as the source.
Obviously, if the include pre-processor is directory-relative (like
{mydfir/myinclude.i}or{../includes/something.i}, 3P should take this relative path in to account.Thanks a lot for this!
Regards,
C.CLEAUD
The text was updated successfully, but these errors were encountered: