search for: set_object

...d changes in packages. Some entry points can safely be added to the API. Around 40 have already been added to WRE with API annotations; another 40 or so can probably be added after review. The remainder mostly fall into two groups: - Entry points that should never be used in packages, such as SET_OBJECT or SETLENGTH (or any non-API SETXYZ functions for that matter) that can create inconsistent or corrupt internal state. - Entry points that depend on the existence of internal structure that might be subject to change, such as the existence of promise objects or internal structure of envir...

...y points can safely be added to the API. Around 40 have > already been added to WRE with API annotations; another 40 or so can > probably be added after review. > > The remainder mostly fall into two groups: > > - Entry points that should never be used in packages, such as > SET_OBJECT or SETLENGTH (or any non-API SETXYZ functions for that > matter) that can create inconsistent or corrupt internal state. > > - Entry points that depend on the existence of internal structure that > might be subject to change, such as the existence of promise objects > or int...

...y points can safely be added to the API. Around 40 have > already been added to WRE with API annotations; another 40 or so can > probably be added after review. > > The remainder mostly fall into two groups: > > - Entry points that should never be used in packages, such as > SET_OBJECT or SETLENGTH (or any non-API SETXYZ functions for that > matter) that can create inconsistent or corrupt internal state. > > - Entry points that depend on the existence of internal structure that > might be subject to change, such as the existence of promise objects > or int...

...y points can safely be added to the API. Around 40 have > already been added to WRE with API annotations; another 40 or so can > probably be added after review. > > The remainder mostly fall into two groups: > > - Entry points that should never be used in packages, such as > SET_OBJECT or SETLENGTH (or any non-API SETXYZ functions for that > matter) that can create inconsistent or corrupt internal state. > > - Entry points that depend on the existence of internal structure that > might be subject to change, such as the existence of promise objects > or int...

...Around 40 have > already been added to WRE with API annotations; another 40 or so > can > probably be added after review. > > The remainder mostly fall into two groups: > > - Entry points that should never be used in packages, such as > ? ?SET_OBJECT or SETLENGTH (or any non-API SETXYZ functions for > that > ? ?matter) that can create inconsistent or corrupt internal > state. > > - Entry points that depend on the existence of internal > structure that > ? ?might be subject to change, such...

there is my code,  expect return value  is a data frame but R say it is list: SEXP Julia_R_MD_NA_DataFrame(jl_value_t* Var) {  SEXP ans,names,rownames;  char evalcmd[4096];  int i;  const char* dfname="DataFrameName0tmp";  jl_set_global(jl_main_module, jl_symbol(dfname), (jl_value_t*)Var);  //Get Frame cols   sprintf(evalcmd,"size(%s,2)",dfname);  jl_value_t*

...een added to WRE with API annotations; another 40 or so > > can > > probably be added after review. > > > > The remainder mostly fall into two groups: > > > > - Entry points that should never be used in packages, such as > > SET_OBJECT or SETLENGTH (or any non-API SETXYZ functions for > > that > > matter) that can create inconsistent or corrupt internal > > state. > > > > - Entry points that depend on the existence of internal > > structure that > >...

...long as callers ignore + any R_UseNamesSymbol attribute when not subscripting with strings, + and the subscript will not be modified in a replacement operation + that it is supplying the subscripts for. */ PROTECT(s = duplicate(s)); SET_ATTRIB(s, R_NilValue); SET_OBJECT(s, 0); +#else + /* Duplicate if the subscript might be being used to replace elements of + itself. */ + if (used_to_replace && NAMED(s) > 0) + s = duplicate(s); + PROTECT(s); +#endif + switch (TYPEOF(s)) { case NILSXP: *stretch = 0; @@ -696,9 +731,9 @@...