bugfix: #line generation for windows

This commit is contained in:
Araq
2011-08-11 01:28:37 +02:00
parent d5dd4669df
commit a1cdd6e7ff
3 changed files with 14 additions and 3 deletions

View File

@@ -18,8 +18,8 @@ proc genLineDir(p: BProc, t: PNode) =
if line < 0:
line = 0 # negative numbers are not allowed in #line
if optLineDir in p.Options and line > 0:
appff(p.s[cpsStmts], "#line $2 \"$1\"$n", "; line $2 \"$1\"$n",
[toRope(toFilename(t.info)), toRope(line)])
appff(p.s[cpsStmts], "#line $2 $1$n", "; line $2 \"$1\"$n",
[makeCString(toFilename(t.info)), toRope(line)])
if ({optStackTrace, optEndb} * p.Options == {optStackTrace, optEndb}) and
(p.prc == nil or sfPure notin p.prc.flags):
appcg(p, cpsStmts, "#endb($1);$n", [toRope(line)])

View File

@@ -2511,7 +2511,7 @@ special ``:`` syntax:
In the example the two ``writeln`` statements are bound to the ``actions``
parameter.
**Note:** Symbol binding rules for templates might change!
**Note:** The symbol binding rules for templates might change!
Symbol binding within templates happens after template instantation:

View File

@@ -48,6 +48,17 @@ version 0.9.XX
- checked exceptions
- fix implicit generic routines
- think about ``{:}.toTable[int, string]()``
- nice idea:
p(a, b):
echo a
echo b
is the same as:
p(a, b, proc() =
echo a
echo b)
Library
-------