Why would R use the “L” suffix to denote an integer?

by

Why is “L” used as a suffix?

I’ve never seen it written down, but I theorise in short for two reasons:

  1. Because R handles complex numbers which may be specified using the
    suffix "i" and this would be too simillar to "I"

  2. Because R’s integers are 32-bit long integers and “L” therefore appears to be sensible shorthand for referring to this data type.

The value a long integer can take depends on the word size. R does not natively support integers with a word length of 64-bits. Integers in R have a word length of 32 bits and are signed and therefore have a range of −2,147,483,648 to 2,147,483,647. Larger values are stored as double.

This wiki page has more information on common data types, their conventional names and ranges.

And also from ?integer

Note that current implementations of R use 32-bit integers for integer vectors, so the range of representable integers is restricted to about +/-2*10^9: doubles can hold much larger integers exactly.

Why do 1.0L and 1.1L return different types?

The reason that 1.0L and 1.1L will return different data types is because returning an integer for 1.1 will result in loss of information, whilst for 1.0 it will not (but you might want to know you no longer have a floating point numeric). Buried deep with the lexical analyser (/src/main/gram.c:4463-4485) is this code (part of the function NumericValue()) which actually creates a int data type from a double input that is suffixed by an ascii "L":

/* Make certain that things are okay. */
if(c == 'L') {
double a = R_atof(yytext);
int b = (int) a;
/* We are asked to create an integer via the L, so we check that the
   double and int values are the same. If not, this is a problem and we
   will not lose information and so use the numeric value.
*/
if(a != (double) b) {
    if(GenerateCode) {
    if(seendot == 1 && seenexp == 0)
        warning(_("integer literal %s contains decimal; using numeric value"), yytext);
    else {
        /* hide the L for the warning message */
        *(yyp-2) = '\0';
        warning(_("non-integer value %s qualified with L; using numeric value"), yytext);
        *(yyp-2) = (char)c;
    }
    }
    asNumeric = 1;
    seenexp = 1;
}
}

More Related Contents:

  1. What specifically are the dangers of eval(parse(…))?
  2. Check if the number is integer
  3. Convert factor to integer [duplicate]
  4. How to convert integer number into binary vector?
  5. How to avoid warning when introducing NAs by coercion
  6. Why does R use partial matching?
  7. What is integer overflow in R and how can it happen?
  8. What’s the difference between integer class and numeric class in R
  9. Clarification of L in R
  10. R: eval(parse(…)) is often suboptimal
  11. How to catch integer(0)?
  12. Finding y-hat in R [closed]
  13. ggplot2 line chart gives “geom_path: Each group consist of only one observation. Do you need to adjust the group aesthetic?”
  14. How can I match fuzzy match strings from two datasets?
  15. Remove parentheses and text within from strings in R
  16. How do you change library location in R? [duplicate]
  17. Understanding dates and plotting a histogram with ggplot2 in R
  18. Legend placement, ggplot, relative to plotting region
  19. sample rows of subgroups from dataframe with dplyr
  20. Display exact value of a variable in R
  21. knitr gets tricked by data.table `:=` assignment
  22. How to index an element of a list object in R
  23. Group data and plot multiple lines
  24. Select last non-NA value in a row, by row
  25. Change the default colour palette in ggplot
  26. How to label a barplot bar with positive and negative bars with ggplot2
  27. Row-wise sort then concatenate across specific columns of data frame
  28. How to adjust facet size manually
  29. R: why kable doesn’t print inside a for loop?
  30. Difference between r-base and r-recommended packages

Leave a Comment