[backport] Add docs to better distinguish among getProjectPath, getCurrentDir and currentSourcePath (#12565)
Fixes https://github.com/nim-lang/Nim/issues/10477.
This commit is contained in:
parent
99078d80d7
commit
d914e9a65f
3 changed files with 42 additions and 5 deletions
|
|
@ -1626,9 +1626,29 @@ macro unpackVarargs*(callee: untyped; args: varargs[untyped]): untyped =
|
|||
result.add args[i]
|
||||
|
||||
proc getProjectPath*(): string = discard
|
||||
## Returns the path to the currently compiling project, not to
|
||||
## be confused with ``system.currentSourcePath`` which returns
|
||||
## the path of the current module.
|
||||
## Returns the path to the currently compiling project.
|
||||
##
|
||||
## This is not to be confused with `system.currentSourcePath <system.html#currentSourcePath.t>`_
|
||||
## which returns the path of the source file containing that template
|
||||
## call.
|
||||
##
|
||||
## For example, assume a ``dir1/foo.nim`` that imports a ``dir2/bar.nim``,
|
||||
## have the ``bar.nim`` print out both ``getProjectPath`` and
|
||||
## ``currentSourcePath`` outputs.
|
||||
##
|
||||
## Now when ``foo.nim`` is compiled, the ``getProjectPath`` from
|
||||
## ``bar.nim`` will return the ``dir1/`` path, while the ``currentSourcePath``
|
||||
## will return the path to the ``bar.nim`` source file.
|
||||
##
|
||||
## Now when ``bar.nim`` is compiled directly, the ``getProjectPath``
|
||||
## will now return the ``dir2/`` path, and the ``currentSourcePath``
|
||||
## will still return the same path, the path to the ``bar.nim`` source
|
||||
## file.
|
||||
##
|
||||
## The path returned by this proc is set at compile time.
|
||||
##
|
||||
## See also:
|
||||
## * `getCurrentDir proc <os.html#getCurrentDir>`_
|
||||
|
||||
when defined(nimMacrosSizealignof):
|
||||
proc getSize*(arg: NimNode): int {.magic: "NSizeOf", noSideEffect.} =
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue