On 4/11/25 17:39, Duncan Murdoch wrote:
On a tangent from the main topic of this thread: sometimes
(especially to non-experts) it's not obvious whether a variable is
protected or not.
I don't think there's any easy way to determine that, but perhaps
there should be. Would it be possible to
That might help, but protecting things is a fairly cheap operation, so I
don't know if people would bother with the naming convention. It's just
as easy to just protect things if you're not sure.
One way things can go wrong is when you think you protected something,
but then the pointer chang
For a long-term horizon, would it help R developers to use a naming
convention?
Perhaps, varName_PROT, or the inverse varName_UNPROT?
Eventually, teach some linter about that?
On Fri, Apr 11, 2025 at 10:40 AM Duncan Murdoch
wrote:
> On a tangent from the main topic of this thread: sometimes (es
On a tangent from the main topic of this thread: sometimes (especially
to non-experts) it's not obvious whether a variable is protected or not.
I don't think there's any easy way to determine that, but perhaps there
should be. Would it be possible to add a run-time test you could call
in C c
