Post Reply 
WP 31S available at SourceForge
04-17-2014, 12:05 PM (This post was last modified: 04-17-2014 12:24 PM by Dieter.)
Post: #11
RE: WP 31S available at SourceForge
(04-17-2014 09:34 AM)walter b Wrote:  d:-/

That's what I think as well. I think between the 31s and 34s there should be as much consistency as possible. IMHO choosing different names for the same commands is not a particulary good idea.

And now for something completely different: the calendar issue, i.e. the switch between the Julian and the current Gregorian calendar. Years ago this topic has been discussed with regard to the 34s. Finally a flag was implemented that switched between the official date (15 Oct 1582) and the one for the British Empire (14 Sept 1752). Not quite a perfect solution, but at least it works for a large part of the world.

However, the 31s does not have that option. It has a fixed setting that's only valid for the British Empire and its colonies. In particular, the "official" date as stated in Inter Gravissimas is ignored.

Since different regions of the world adopted the new calendar in different years, I think there are only two solution that really make sense:
  1. If no option is given, the fixed switch should be between 4 and 15 Oct 1582, as stated in the official document. This is the solution all calendar programs I know of work with. Even TI did so in their ML-20 program. ;-)
  2. Make the switch date user-selectable, so that everyone can use the correct date for his/her region. For instance with 15,101582 JGSET. This solution has two major advantages:
    • It will work for absolutely every region in the world and not just for two large blocks as it does now on the 34s.
    • It extends the functionality of the date commands because now even calculations based on a so called proleptic Julian or Gregorian calendar become possible. Which means that the Julian resp. Gregorian calendar is assumed for any date.

The 31s now gives us the opportunity to realize an improvement that has not made it into the 34s. On the other hand, if there is no user-selectable switch date, the only valid solution in my humble opinion is a fixed 15 Oct 1582, which is consistent with most other calendar software as well as ISO 8601. However, I think we can do better. Walter, Pauli and all others: let's have the user make his choice. My vote clearly goes to a JGSET command. On the 31s as well as on the 34s. Consider it a bug-fix. ;-)

Dieter
Find all posts by this user
Quote this message in a reply
Post Reply 


Messages In This Thread
WP 31S available at SourceForge - walter b - 04-15-2014, 07:49 AM
RE: WP 31S available at SourceForge - Dieter - 04-17-2014 12:05 PM
RE: WP 31S available at SourceForge - Bit - 04-17-2014, 05:27 PM
WP 31S inquest - walter b - 04-30-2014, 10:31 AM
RE: WP 31S inquest - walter b - 04-30-2014, 11:20 AM
RE: WP 31S available at SourceForge - JimP - 05-02-2014, 11:18 PM
RE: WP 31S available at SourceForge - nsg - 07-16-2014, 01:18 AM
RE: WP 31S available at SourceForge - Bit - 11-13-2014, 05:11 AM
RE: WP 31S available at SourceForge - Bit - 11-13-2014, 01:22 PM
RE: WP 31S available at SourceForge - Bit - 11-13-2014, 04:35 PM
RE: WP 31S available at SourceForge - Bit - 11-16-2014, 04:35 AM
RE: WP 31S available at SourceForge - Bit - 11-17-2014, 01:52 AM
RE: WP 31S available at SourceForge - Bit - 01-31-2015, 03:01 PM
RE: WP 31S available at SourceForge - Bit - 11-17-2014, 01:12 AM



User(s) browsing this thread: 2 Guest(s)