|
|
Subscribe / Log in / New account

A GNU COBOL status update

For the COBOL users out there, James K. Lowden has posted an update on the current status of the GNU COBOL compiler.

When in November we turn back our clocks, then naturally do programmers' thoughts turn to Cobol, its promise, and future.

At last post, nine months ago, we were working our way through the NIST CCVS/85 test suite. I am pleased to report that process is complete. As far as NIST is concerned, gcobol is a Cobol compiler.



to post comments

A GNU COBOL status update

Posted Nov 15, 2023 13:55 UTC (Wed) by grawity (subscriber, #80596) [Link] (1 responses)

This is apparently COBOL for the GNU Compiler Collection, and not the same thing as the older GnuCOBOL project?

A GNU COBOL status update

Posted Nov 15, 2023 17:52 UTC (Wed) by rahulsundaram (subscriber, #21946) [Link]

> This is apparently COBOL for the GNU Compiler Collection, and not the same thing as the older GnuCOBOL project?

Yes. gcobol which project is an independent implementation is intended to be part of GCC while GNUCobol (originally OpenCOBOL before it became a GNU project) is a transpiler to C.

A GNU COBOL status update

Posted Nov 15, 2023 14:26 UTC (Wed) by Flameeyes (guest, #51238) [Link] (7 responses)

> When in November we turn back our clocks, then naturally do programmers' thoughts turn to Cobol, its promise, and future.

Wut?

A GNU COBOL status update

Posted Nov 15, 2023 17:38 UTC (Wed) by smurf (subscriber, #17840) [Link] (4 responses)

What's "Wut" about that? When you're talking about computers there's "turning back the clocks", and then there's COBOL.

That language cannot be too many decades in the past, IMHO.

A GNU COBOL status update

Posted Nov 15, 2023 18:05 UTC (Wed) by Flameeyes (guest, #51238) [Link] (3 responses)

Am I to assume this is a type of in-joke that is going to be totally obtuse to anyone under 40? (50? 60?)

I'm in no sarcastic way not understanding what the connection would be between turning back clocks and COBOL.

Unless *everything* to do with computer goes back to COBOL in the mind of the author which could be understandable, but would worry me nonetheless.

A GNU COBOL status update

Posted Nov 15, 2023 18:08 UTC (Wed) by willy (subscriber, #9762) [Link] (2 responses)

Turning back the clocks -> going back in time -> working on a dead language

A GNU COBOL status update

Posted Nov 15, 2023 18:29 UTC (Wed) by Flameeyes (guest, #51238) [Link] (1 responses)

🤦

Okay I wouldn't have made that particular leap. Thanks!

A GNU COBOL status update

Posted Nov 18, 2023 7:50 UTC (Sat) by ssmith32 (subscriber, #72404) [Link]

If it makes you feel better, I thought it was a reference to Y2K, and all the hemming and hawing about COBOL programs not handling time (and say, quirky things like DST) very well.

A GNU COBOL status update

Posted Nov 15, 2023 18:26 UTC (Wed) by ballombe (subscriber, #9523) [Link] (1 responses)

This is a reference to daylight saving time.

A GNU COBOL status update

Posted Nov 16, 2023 8:28 UTC (Thu) by kaesaecracker (subscriber, #126447) [Link]

Because that one is also supposed to be dead but obviously still very alive?

A GNU COBOL status update

Posted Nov 15, 2023 19:17 UTC (Wed) by sammythesnake (guest, #17693) [Link] (13 responses)

Meanwhile, here in the UK, our clocks go back in October because dates aren't obtuse enough without every third time zone having it's own rules in when/whether/how far the clocks change for DST.

When I Rule The Worldâ„¢ I'll change the orbit &v rotation of Earth a little so we have a 25 hour day, a 400 day year, and 10 months reach of 4x 10-day weeks.

Vote for me!

A GNU COBOL status update

Posted Nov 15, 2023 20:33 UTC (Wed) by smurf (subscriber, #17840) [Link]

*its* own rules, dammit.

So, no vote for you.

[OT] Time zones, etc (was A GNU COBOL status update)

Posted Nov 15, 2023 23:34 UTC (Wed) by dskoll (subscriber, #1630) [Link] (11 responses)

Interesting... the Earth's rotational kinetic energy is 2.138 * 10^29 J. Slowing its rotational period to 25h would require the dissipation of 1.676 * 10^28 J. That's a mere quadrillion Hiroshima atomic bombs, give or take, so there could be a slight logistical difficulty...

[OT] Time zones, etc (was A GNU COBOL status update)

Posted Nov 16, 2023 0:04 UTC (Thu) by Cyberax (✭ supporter ✭, #52523) [Link] (10 responses)

You can use a correctly-sized asteroid hitting the Earth as just the right angle.

[OT] Time zones, etc (was A GNU COBOL status update)

Posted Nov 16, 2023 1:01 UTC (Thu) by ErikF (subscriber, #118131) [Link] (9 responses)

Alternatively, you could simply redefine the second. I'm sure that's not too difficult. :-)

[OT] Time zones, etc (was A GNU COBOL status update)

Posted Nov 17, 2023 20:09 UTC (Fri) by rgmoore (✭ supporter ✭, #75) [Link] (8 responses)

You can redefine the second to get a 25 hour day, but you have to make some kind of physical change to the Earth's rotation or orbit to get a 400 day year. I would suggest the least drastic move that would actually improve the calendar would be to slow the Earth's rotation just enough to get a year of exactly 364 days. That would allow a year of exactly 52 weeks, so the year would always start on the same day of the week. Of course we'd have to eliminate the moon so our rotation wouldn't be slowed by tides...

[OT] Time zones, etc (was A GNU COBOL status update)

Posted Nov 17, 2023 20:35 UTC (Fri) by Wol (subscriber, #4433) [Link] (1 responses)

And I heard tell that Napoleon tried to decimalise time. That 10-day week *really* didn't work out well.

At my workplace (and I think it's EU rules) many people are simply NOT ALLOWED to work more than six consecutive days, on safety grounds.

Cheers,
Wol

[OT] Time zones, etc (was A GNU COBOL status update)

Posted Nov 17, 2023 21:28 UTC (Fri) by mpr22 (subscriber, #60784) [Link]

The Republican calendar instituted in 1793 had nothing to do with Boney.

Boney abolished the ten-day week in 1802, after making nice with the man beyond the mountains, and then the Republican calendar in its entirety on 1 January 1806, a little over a year after being crowned Emperor of the French).

[OT] Time zones, etc (was A GNU COBOL status update)

Posted Nov 18, 2023 7:52 UTC (Sat) by ssmith32 (subscriber, #72404) [Link] (1 responses)

Redefine day..

[OT] Time zones, etc (was A GNU COBOL status update)

Posted Nov 20, 2023 7:42 UTC (Mon) by eduperez (guest, #11232) [Link]

A second is an arbitrary unit of measurement, all it takes to change it is a general consensus; but day and year have a physical meaning.

[OT] Time zones, etc (was A GNU COBOL status update)

Posted Nov 18, 2023 13:11 UTC (Sat) by geert (subscriber, #98403) [Link] (1 responses)

That would be unfair: some people would always have to celebrate their birthday on a weekday, while others could always celebrate on a Sunday ;-)
(replace weekday and Sunday by the days of your liking)

Correct birthdays.

Posted Nov 18, 2023 19:29 UTC (Sat) by gmatht (guest, #58961) [Link]

This reminds me of the science fiction story. The solution is to induce labour on the correct day.

[OT] Time zones, etc (was A GNU COBOL status update)

Posted Nov 19, 2023 21:32 UTC (Sun) by NYKevin (subscriber, #129325) [Link] (1 responses)

There have actually been multiple proposed calendar reforms that would've eliminated the changing days of the week, usually by introducing an intercalary day (i.e. a day that is not counted as any day of the week). Of those, the World Calendar probably got the closest to being implemented, but various religious groups opposed it (on the grounds of "my holy day falls every seven days, and fiddling with the calendar would mess that up").

If it had been implemented, the World Calendar would have introduced a three-day weekend beginning on Saturday, December 30* and ending on Sunday, January 1, with the middle day being called "Worldsday" and having no day of the week (or month, for that matter). In leap years, another intercalary day is inserted between Saturday, June 30, and Sunday, July 1. The calendar has the same number of days as the Gregorian calendar and uses the same leap year formula, so there would be no need to add or subtract days in order to switch to it (as was done with the Gregorian reform).

If you want something more standard and widely-supported, you could use the ISO 8601 week-numbering year, which always has a whole number of weeks, but usually does not agree with the Gregorian calendar as to the nth day of the year. The week-numbering year works by labeling whichever week contains the first Thursday in January (according to the Gregorian calendar) as "week 1," and then numbering weeks consecutively until you get to "week 1" of the following year. This means that, for example, if a year begins on Wednesday (according to the Gregorian Calendar), then the week-numbering calendar says it begins on December 30 (the preceding Monday). If a year begins on Monday, then both calendars agree on the beginning of the year, and the nth day of the year, but they will disagree as to when it ends. Because the week-numbering year defines its starting point relative to the Gregorian calendar, it cannot fall too far "out of sync," and periodically makes up for the lost days by having 53 weeks in a year. No individual year is closely aligned with the tropical year, but in the long run, the discrepancies cancel out.

Unfortunately, there's probably no good way to combine these types of reform: You can either have a year that follows the tropical year, as the Gregorian and World calendars are, or you can have a whole number of weeks, as the ISO week-numbering year does, but you can't do both.

* The calendar shortens December to 30 days, as part of a broader reform intended to produce more consistent month durations and four equal quarters.

[OT] Time zones, etc (was A GNU COBOL status update)

Posted Nov 20, 2023 17:15 UTC (Mon) by Wol (subscriber, #4433) [Link]

A lot of calendars are actually that sort of calendar (usually lunar calendars).

It mildly annoys me when Easter is called "a moveable feast". It isn't, it's the first Sunday of the first month of the New Year. Just not our modern Gregorian New Year.

I gather the old Roman Calendar only had ten months, and was also a lunar calendar. It started roughly on the Spring Equinox, ran ten months to end roughly on the Winter Solstice, and then the calendar stopped for Winter until the new calendar started on the next spring equinox.

(Easter - with certain ecclesiastical fixes - is defined as the "first Sunday after the first full moon after the Spring Equinox". So if New Year's Day is the Spring Equinox - which it sort of was, I'm not sure if it was the 21st or 25th March, the first moonth was the first "full moon to full moon" of the year. Passover has approximately the same definition, but Passover has nothing to do with Sunday, and if Passover falls on a Sunday, Easter is the following Sunday. I think that only happens if Passover falls on a full moon.)

Cheers,
Wol


Copyright © 2023, Eklektix, Inc.
Comments and public postings are copyrighted by their creators.
Linux is a registered trademark of Linus Torvalds