From simon.urbanek at r-project.org  Tue Apr 29 17:09:23 2014
From: simon.urbanek at r-project.org (Simon Urbanek)
Date: Tue, 29 Apr 2014 11:09:23 -0400
Subject: [Rd] C API for parse error
In-Reply-To: <1398767981512-4689662.post@n4.nabble.com>
References: <1398767981512-4689662.post@n4.nabble.com>
Message-ID: <7E779079-3D9D-4B04-BE0E-E8065F7C8656@r-project.org>

On Apr 29, 2014, at 6:39 AM, JaiReddy <avula.jayakrishna at gmail.com> wrote:

> May I know if we have any C api(or any other way) in retrieving the parse error message after calling R_ParseVector?
> 

R_ParseErrorMsg

But AFAICS it's not part of the API, so beware (although it's not hidden). By now I think it's safer to use try(parse(text=), silent=TRUE) which gives you the full error with details (the Msg is only one part). It could be worthwhile to think about exposing a C-level API to all the R_ParseError* pieces, though - but I'll leave that to the parser experts since only they know if this is now stable enough.

Cheers,
Simon


> 
> --
> View this message in context: http://r.789695.n4.nabble.com/C-API-for-parse-error-tp4689662.html
> Sent from the R devel mailing list archive at Nabble.com.
> 
> ______________________________________________
> R-devel at r-project.org mailing list
> https://stat.ethz.ch/mailman/listinfo/r-devel
> 



[Rd] C API for parse error
Simon Urbanek