Log Message:
(geography/R-deldir) Updated 1.0.9 to 2.0.4

 Version 2.0-4 27/02/2024

 Added an informative (???) error message to handle the setting
 in which all points lie on a vertical or horizontal straight line
 (whence the rectangular window cannot be inferred from the data).

 Version 2.0-3 06/12/2023

 Added the argument "axes" to plot.tile.list(), to permit the
 suppression of the plotting of axes marked with a numeric scale.
 Argument added at the request of Damon Tutunjia.

 Adjust the help file for plot.tile.list().

 Changed the startup message.

 Also changed the  nickname.

 Version 2.0-2 20/11/2023

 Changed my (the maintainer's) email address to
 rolfturner@posteo.net.  Made this change in the DESCRIPTION file
 and in the help files.  Introduced a macro "\rolf" to go into the
 \author{ } field so that future changes can be effected simply by
 changing the macro.  Version 2.0-2 is now up on CRAN.

 Version 2.0-1 20/11/2023

 Corrected a couple of rather silly bugs (which took an enormous
 amount of time and effort to track down) in trifnd.f90 and stoke.f90.
 Both bugs involved incorrect Fortran 90 if/else syntax.

 Version 2.0-0 20/11/2023

 Converted ratfor code to fortran 90 code (placing the latter
 into the "src" directory).

 Version 1.0-12 23/11/2023

 While debugging the new Fortran 90 based version (see above) of this
 package it became clear that an if/else structure in trifnd.r was
 (although not actually wrong) ill-constructed.  I corrected this
 defect, making the code consistent with the corresponding code
 in trifnd.f90.

 Version 1.0-11 18/11/2023

 Changed insidePoly() so that tolerance can be specified by the used,
 rather than being hardwired to the value sqrt(.Machine$double.eps).
 This necessitated changing the structure of insidePoly.R so as *not*
 to use local().

 Version 1.0-10 17/11/2023

 Corrected a bug in insidePoly(); I had misunderstood the
 sanity check in spatstat.utils::inside.xypolygon(), which issues
 a *warning* if not all entries of "score" are 0 or 1, but describes
 this as being an "internal error".  So I had made insidePoly() throw
 an error in this circumstances; I shouldn't have!  The errors thrown
 are spurious.  I have now changed the error to a warning, and added
 an argument "sanityCheck=FALSE"; the warning is issued only if
 sanityCheck is set to TRUE.

 Also introduced "%~%" (almost equal).  Using this in place of \ 
"=="
 seems (???) to do a better job of determining  boundary points
 correctly.

 Thanks to Huimin Wang whose enquiry about inexplicable crashes in
 tileInfo() disclosed the aforementioned bug.`