Why not use a different namespace?

Issue #59 resolved
Torsten Curdt created an issue

"The library has been developed to replace the current Arduino library, therefore you will need to remove/backup the LiquidCrystal folder from the Arduino library folder the original LiquidCrystal library and replace it for this one. You will also potentially need to remove other LCD libraries like LiquidCrystal_I2C as that will also conflict with this library."

This make installing and using it quite painful. Why not use a different namespace?

Comments (6)

  1. Francisco Malpartida repo owner

    I did consider it at the time but when the library came about, you had to copy manually any library to the IDE library folder. You then have a lot of users that would end up having to go with using the name space. For many users would cause more problems than just removing the old one and replacing the new one. Let's say that most users see Arduino as a programming language instead of C++ and name spaces are not used. Finally it would imply for people to have to change their code to start using the new namespace.

    In any case I will give it good thought for a mayor release. I you would like to contribute to the library with this change please do, fork and get a merge request through.

  2. Torsten Curdt reporter

    Sorry for the confusion - I didn't actually mean C++ namespaces. I meant

    #include <NewLiquidCrystal.h>
  3. Francisco Malpartida repo owner

    Currently you have LCD.h which is the main entry point to the entire library. But I don't think it will cut the butter. At least if they haven't changed the way the compilation backend works. Give it a try and let me know. LiquidCrystal.h is only used for the 4 bit parallel replacement.

  4. Torsten Curdt reporter

    Not sure I can follow. My concern was to be able to (easily) have different versions of "LiquitCrystal.h" in my library.

  5. Log in to comment