Skip to content
Prev 70067 / 398506 Next

R annoyances

Dear John,

I have not expected to cause that many traffic and largish discussion.

What I tried to point out is that:
- a "programmer" should know that one has to use TRUE / FALSE in code in 
order to make it work generaly which is also checked by R CMD check.
- a "user" simply typing some lines in order to look at the data can 
shortly write T or F instead.

where "programmer" and "user" are not well defined and probably 
undistinguishable according to Chambers (1998).
I'd call people using [..., drop=FALSE] "programmer" here, since the 
code is probably used inside functions.

S-PLUS compatibility (T/F) has to be considered as well.

All possible changes to T/F (both removing the meaning of TRUE/FALSE in 
a clean session and making them reserved words) would break code of lots 
of users. With a common amount of statistical uncertainty I think it 
might be too late for changes ...

Best,
Uwe
John Fox wrote: