You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I was testing out the feasibility of running non-precompiled fennel code on windows and ran into the following windows sepcific error.
(require :colour)
runtime error: ./colour.fnl:105: unfinished string near '"Convert HSL to RGB. '
stack traceback:
[C]: in function 'assert'
./fennel:878: in function 'load-code'
./fennel:3838: in function ?
[C]: in function 'chunk'
./fennel:432: in function ?
[C]: in function 'xpcall'
./fennel:437: in function 'repl'
./fennel:4529: in function ?
[C]: in ?
The error occurs in the docstring of a function.
(fn colour.hsl-to-rgb [hin s l a]
"Convert HSL to RGB. Note A remains unchanged."
(var [r g b] [000])
...
It can be fixed by removing all newlines from the docstring or changing the line endings from DOS to UNIX.
Would it be feasible to handle multiple types of line endings in the docstring parser? If not, perhaps a note on this limitation should be included in the documentation on docstrings?
The text was updated successfully, but these errors were encountered:
Resolves#354 (on github)
This updates the doc special so that it checks if running in windows
(stupidly, by comparing the path separator against "\\"), and
conditionally outputs the docstring with \n replaced by \r\n.
This also conditionally modifies the docstring test cases when run on
windows.
Resolves#354 (on github)
This updates the doc special so that it checks if running in windows
(stupidly, by comparing the path separator against "\\"), and
conditionally outputs the docstring with \n replaced by \r\n.
This also conditionally modifies the docstring test cases when run on
windows.
Also, attempting to re-enable the circleci windows tests to see if
they're working again.
I was testing out the feasibility of running non-precompiled fennel code on windows and ran into the following windows sepcific error.
The error occurs in the docstring of a function.
It can be fixed by removing all newlines from the docstring or changing the line endings from DOS to UNIX.
Would it be feasible to handle multiple types of line endings in the docstring parser? If not, perhaps a note on this limitation should be included in the documentation on docstrings?
The text was updated successfully, but these errors were encountered: