[Rd] defer removal of ENCLOS, FRAME, HASHTAB, SET_ENCLOS

[Simon Urbanek]

Laurent,

see R-exts 6.22 [1] in particular subsections 1 and 2. As for FRAME you use the accessor functions instead of accessing it directly.

Cheers,
Simon

[1] - https://cran.r-project.org/doc/manuals/r-devel/R-exts.html#Moving-into-C-API-compliance


> On 22 Mar 2026, at 12:00, Laurent Gautier <lgautier using gmail.com> wrote:
> 
> Hi,
> 
> I'd like to second that request. rpy2, a Python-R bridge, also
> uses ENCLOS / SET_ENCLOS and to a lesser extent FRAME.
> 
> Also, what is the alternative suggested to replace the functionality
> they offered?
> 
> 
> Best,
> 
> Laurent
> 
> 
> 
> Hi,
>> 
>> The development version of R removes the symbols
>> 
>>    ENCLOS, FRAME, HASHTAB, SET_ENCLOS
>> 
>> as per r89522. Unfortunately, these symbols are used by current
>> versions of RStudio, and so these versions of RStudio are unable to
>> launch with the development versions of R. (By extension, they would
>> also fail to launch using R 4.6.0 when released.)
>> 
>> On the RStudio side, we can work to adapt to these changes as quickly
>> as possible, but our experience is that users will often upgrade R
>> without necessarily upgrading RStudio in tandem.
>> 
>> I'd like to propose keeping these symbols defined in R for now (even
>> if not publicly accessible via headers) just to ensure existing
>> versions of RStudio can continue to function as expected with the
>> upcoming release of R.
>> 
>> Thanks,
>> Kevin
>> 
>> 
> 
> [[alternative HTML version deleted]]
> 
> ______________________________________________
> R-devel using r-project.org mailing list
> https://stat.ethz.ch/mailman/listinfo/r-devel
>