Prof Brian Ripley wrote:
> I think the question is how are you accessing the parser? The only
> public interface is R_ParseVector, and that works like parse(text=):
Yes, I'm using R_ParseVector. PL/R basically takes the function's text
as stored in the Postgres system catalog table (prosrc fiel
I think the question is how are you accessing the parser? The only public
interface is R_ParseVector, and that works like parse(text=):
> parse(text="abc\ndef")
expression(abc, def)
attr(,"srcfile")
> parse(text="abc\r\ndef")
Error in parse(text = "abc\r\ndef") :
" syntax error, unexpected $und
I've recently ported PL/R (R embedded in Postgres as a procedural
language) to work on Win32 -- thank you to all involved for making the
embedded interface common between *nix and Win32!
This of course means users are now creating PL/R functions using Win32
based editors, which are using \r\n f
