EViews 处理文件路径问题
EViews 7.1在处理文件路径规范方面提供了改进的功能，包括对".\"和 "..\" 前缀相对路径的扩展支持 。不幸的是，其中一些新功能与早期版本的EViews中解释的相对路径相冲突。下面的讨论概述了路径行为的变化。
EViews 7.1 and Later Behavior
Context(no prefix).\..\.\..\
Includerunpathlinepathabove runpathabove linepath
Execaddinslinepathabove addinsabove linepath
Run/Open/CD/Otherevdatalinepathabove evdataabove linepath
EViews 7 and Earlier Behavior
Context(no prefix).\..\.\..\
Includerunpathrunpathabove runpath---
Exec------------
Run/Open/CD/Otherevdataevdataabove evdata---
• linepath is the location of the program file containing the currently executed line. Thus in an included file, it will contain the location of the "child" program, not the location of the "parent" program.
• runpath is the location of the program file that is "running", where execution via exec or include does not count as "running". Thus if you run a program that contains included or execs, runpath in those included/exec'd files will refer to the location of the parent file, not the subprogram files. If a program was exec'd from the command line, then runpath will refer to the EViews data directory.
• addins is the location of the add‐ins directory
• evdata is the current EViews default directory
It is worth noting that the following string functions may be used to obtain the locations of these directories:
• @addinspath ‐ the location of the add‐ins directory
• @datapath – the location of the current EViews data directory
• @linepath – the location of the currently executed line
• @runpath – the location of the program that is "running", where execs and includes do not count as "running".
Note also that the special "<addins>" keyword may be used as part of a path to indicate the addins directory.
刚准备学eviews，先下载看看先，谢谢楼主的分享
页:
[1]