search for: nonexport

...or outputs and character(0) for list outputs and nomatch = NA results in insertion of NA_character_, and nomatch = '' results in insertion of empty string. I can submit proposed patch code if others think this is a good idea. What are your thoughts on the proposed alteration to (currently nonexported) strextract? I assume (maybe wrongly) that the plan is to eventually export that function. Thank you, CG

You need to learn how to access code for nonexported methods. See ? "::" > methods(qda) [1] qda.data.frame* qda.default* qda.formula* qda.matrix* see '?methods' for accessing help and source code Shows you that the methods are not exported from the namespace. Hence you need to use the triple colon operator to see their...

Hello, I am Souradeep Chattopadhyay and I am a graduate student at Iowa State University Department of Statistics. Can anyone please explain the mathematical formulation behind the scaling matrix returned by the qda function in MASS package. I want to understand how this scaling matrix is derived from the inputs given to the qda function. Example Code The following example is using

...urse but to muck through source code. Btw, I think the following will give the necessary source code: MASS:::qda.default Hope this helps! Best wishes, Ranjan On Wed, 23 Aug 2017 15:58:30 -0700 Bert Gunter <bgunter.4567 at gmail.com> wrote: > You need to learn how to access code for nonexported methods. See ? "::" > > > methods(qda) > [1] qda.data.frame* qda.default* qda.formula* qda.matrix* > see '?methods' for accessing help and source code > > Shows you that the methods are not exported from the namespace. Hence > you need to use the...

...ist > outputs and nomatch = NA results in insertion of NA_character_, and nomatch > = '' results in insertion of empty string. > > I can submit proposed patch code if others think this is a good idea. > > What are your thoughts on the proposed alteration to (currently > nonexported) strextract? I assume (maybe wrongly) that the plan is to > eventually export that function. > > Thank you, > CG > [[alternative HTML version deleted]]

...ource the class definition. That is, if class1 features global constant CONSTANT=3, then if class2 sources class1, it will also include the constant. This 1) clutters the namespace when running the code interactively, 2) potentially overwrites the constants in case of nameclash. Some kind of export/nonexport variable syntax, or symbolic import, or namespace would be useful. I know if I converted it to a package I would get at least something like a namespace, but still. I understand that the variable cannot just not be imported, in general, as the functions will generally rely on it (otherwise it woul...

...atch = NA results in insertion of NA_character_, and nomatch >> = '' results in insertion of empty string. >> >> I can submit proposed patch code if others think this is a good idea. >> >> What are your thoughts on the proposed alteration to (currently >> nonexported) strextract? I assume (maybe wrongly) that the plan is to >> eventually export that function. >> >> Thank you, >> CG >> > [[alternative HTML version deleted]]

A very common use case for regmatches is to extract regex matches into a new column in a data.frame (or data.table, etc.) or otherwise use the extracted strings alongside the input. However, the default behavior is to drop empty matches, which results in mismatches in column length if reassignment is done without subsetting. For consistency with other R functions and compatibility with this use

...ource the class definition. That is, if class1 features global constant CONSTANT=3, then if class2 sources class1, it will also include the constant. This 1) clutters the namespace when running the code interactively, 2) potentially overwrites the constants in case of nameclash. Some kind of export/nonexport variable syntax, or symbolic import, or namespace would be useful. I know if I converted it to a package I would get at least something like a namespace, but still. > > I understand that the variable cannot just not be imported, in general, as the functions will generally rely on it (otherwis...

...ource the class definition. That is, if class1 features global constant CONSTANT=3, then if class2 sources class1, it will also include the constant. This 1) clutters the namespace when running the code interactively, 2) potentially overwrites the constants in case of nameclash. Some kind of export/nonexport variable syntax, or symbolic import, or namespace would be useful. I know if I converted it to a package I would get at least something like a namespace, but still. >> >> I understand that the variable cannot just not be imported, in general, as the functions will generally rely on it...

...ource the class definition. That is, if class1 features global constant CONSTANT=3, then if class2 sources class1, it will also include the constant. This 1) clutters the namespace when running the code interactively, 2) potentially overwrites the constants in case of nameclash. Some kind of export/nonexport variable syntax, or symbolic import, or namespace would be useful. I know if I converted it to a package I would get at least something like a namespace, but still. >>> >>> I understand that the variable cannot just not be imported, in general, as the functions will generally rely...