This can help when using Scintilla views as command line widgets.
It can also help when using Scintilla to edit binary files as you
don't want to attach special meaning to CR and LF.

This patch will not be merged for the time being, so we strive
to reduce the number of touched lines.
See https://groups.google.com/g/scintilla-interest/c/iE6E4n9zWT4

warnings.

Report changed range for Document::SetStyleFor.

* This is the case e.g. on NetBSD 10 for ARMv6 where Sci::Position == ptrdiff_t == long int,
  but obviously for other platforms as well, where it causes "invalid conversion"
  and "undefined symbol" errors.
  Scintilla was testing for aliasability by comparing the storage size with sizeof()
  or PTRDIFF_MAX == INT_MAX at the preprocessor level.
  This was fundamentally flawed.
* In LineVector<T>::InsertLines() we are now using the C++17 construct
  std::is_convertible_v<From*,To*> instead.
* We need RunStyles<ptrdiff_t> as well on the affected platforms.
  This is impossible to test for in a constant expression that can be used
  with the preprocessor.
  Also, it's not possible to conditionally instantiate templates.
  We tried to instantiate RunStyles for all scalar types that could be behind ptrdiff_t,
  but it was causing warnings on MSVC.
  Implicitly instantiating RunStyles would be possible, but is not desired.
  Therefore as a workaround, you can now define the PTRDIFF_DOESNT_ALIAS_INT
  macro when invoking the build system, to force instantiating RunStyles<ptrdiff_t>.
  When writing portable applications, you may have to use a compile-time check
  for checking aliasability of ptrdiff_t and int in order to define PTRDIFF_DOESNT_ALIAS_INT.

nesting depth.