floresta:
There used to be no such thing as LCD.println before Arduino 1.0 (or around that version).
Well there still is 'no such thing' if you look at the documentation for the LiquidCrystal library.
So if I understand correctly, in older Arduini IDE versions the use of LCD.println would have resulted in an error of some kind but now there is none since there really is no error, just some unusual behavior due to the characteristics of the LCD controller that I explained in reply #5.
By not mentioning println in the LiquidCrystal documentation the powers that be are essentially absolving themselves of responsibility for this strange (to the uninitiated) behavior. It seems to me that it would be more responsible to mention why println was omitted from the documentation.
Don
Right, undocumented but exists through inheritance. The potential problem of inheritance is showing its color here with LCD lib. You make a bunch of these functions in your base class and your child class inherits these functions but not all are working with the child class. The base class does nothing special other than printing 0D and 0A, assuming the receiving device understands it. But the child class hardware (LCD) is not exactly a super set of the base class hardware (computer serial monitor). A child should have all base plus extra but this case it is not. The base class should probably declare println as virtual so a child class has to define it to use it. We have a bunch of newbies that don't know these subtleties and think they can use println anywhere it won't complain. In an extreme case, say a base class defines .kill_self() and the child class commits suicide with .kill_self() but finds the method doesn't really apply to the child due to different hardware, maybe the child is a cylon and inherits from human parents, the child may become zombie or something LOL