search for: s3_method_markup_regexp

...\method{@}{newclass}(object, name) <- value Throws this error during R CMD check ?as-cran Bad \usage lines found in documentation object ?code?: <unescaped bksl>method{@}{newclass}(object, name) <- value This error is due to tools::checkDocFiles eventually calling tools:::.S3_method_markup_regexp and not finding `@` as a valid for S3. This error is gone if we adjust tools:::.S3_method_markup_regexp to pass for ?@? by adding ?\\@? to regexp. Please note that this now is not dependant on using or not using roxygen2 KK. > On Apr 29, 2023, at 12:53 AM, Karolis Koncevi?ius <karolis.konce...

...}(object, name) <- value > Throws this error during R CMD check ?as-cran > Bad \usage lines found in documentation object ?code?: > <unescaped bksl>method{@}{newclass}(object, name) <- value > This error is due to tools::checkDocFiles eventually calling tools:::.S3_method_markup_regexp and not finding `@` as a valid for S3. > This error is gone if we adjust tools:::.S3_method_markup_regexp to pass for ?@? by adding ?\\@? to regexp. > Please note that this now is not dependant on using or not using roxygen2 > KK. >> On Apr 29, 2023, at 12:53 AM, Karolis Koncevi?iu...

...gt; >> Throws this error during R CMD check ?as-cran > >> Bad \usage lines found in documentation object ?code?: >> <unescaped bksl>method{@}{newclass}(object, name) <- value > >> This error is due to tools::checkDocFiles eventually calling tools:::.S3_method_markup_regexp and not finding `@` as a valid for S3. >> This error is gone if we adjust tools:::.S3_method_markup_regexp to pass for ?@? by adding ?\\@? to regexp. > >> Please note that this now is not dependant on using or not using roxygen2 >> KK. > >>> On Apr 29, 2023, at 12...

...this error during R CMD check ?as-cran >> >>> Bad \usage lines found in documentation object ?code?: >>> <unescaped bksl>method{@}{newclass}(object, name) <- value >> >>> This error is due to tools::checkDocFiles eventually calling tools:::.S3_method_markup_regexp and not finding `@` as a valid for S3. >>> This error is gone if we adjust tools:::.S3_method_markup_regexp to pass for ?@? by adding ?\\@? to regexp. >> >>> Please note that this now is not dependant on using or not using roxygen2 >>> KK. >> >>>&gt...

...during R CMD check ?as-cran >>> >>>> Bad \usage lines found in documentation object ?code?: >>>> <unescaped bksl>method{@}{newclass}(object, name) <- value >>> >>>> This error is due to tools::checkDocFiles eventually calling tools:::.S3_method_markup_regexp and not finding `@` as a valid for S3. >>>> This error is gone if we adjust tools:::.S3_method_markup_regexp to pass for ?@? by adding ?\\@? to regexp. >>> >>>> Please note that this now is not dependant on using or not using roxygen2 >>>> KK. >>&...

...deeper - I was not successful in passing R CMD checks for the usage files. R CMD check kept showing errors for `@` declarations, even thou they were identical to `$` declarations (which passed fine). >> >> Seems like the usage check functions are not prepared for `@` - also in tools:::.S3_method_markup_regexp >> >> > On Apr 28, 2023, at 10:34 PM, Karolis Koncevi?ius <karolis.koncevicius at gmail.com <mailto:karolis.koncevicius at gmail.com>> wrote: >> > >> > I was building a package that uses the new generic @ and kept having errors with ?roxygen2? document...

...is issue might go deeper - I was not successful in passing R CMD checks for the usage files. R CMD check kept showing errors for `@` declarations, even thou they were identical to `$` declarations (which passed fine). Seems like the usage check functions are not prepared for `@` - also in tools:::.S3_method_markup_regexp > On Apr 28, 2023, at 10:34 PM, Karolis Koncevi?ius <karolis.koncevicius at gmail.com> wrote: > > I was building a package that uses the new generic @ and kept having errors with ?roxygen2? documentation. ?roxygen2? generated NAMESPACE added `@.newclass` as a newly exported functio...

...- I was not successful in passing R CMD checks > for the usage files. R CMD check kept showing errors for `@` declarations, > even thou they were identical to `$` declarations (which passed fine). > > Seems like the usage check functions are not prepared for `@` - also in > tools:::.S3_method_markup_regexp > > > On Apr 28, 2023, at 10:34 PM, Karolis Koncevi?ius < > karolis.koncevicius at gmail.com> wrote: > > > > I was building a package that uses the new generic @ and kept having > errors with ?roxygen2? documentation. ?roxygen2? generated NAMESPACE added > `@.new...

I was building a package that uses the new generic @ and kept having errors with ?roxygen2? documentation. ?roxygen2? generated NAMESPACE added `@.newclass` as a newly exported function, not as a S3method. At first I thought this must be a bug in roxygen2 and they lag behind the new developments in R. But after some investigation I found that ?roxygen2? is using tools:::.get_internal_S3_generis()