I have't seen any mention here about the VMS Software Bootcamp coming up
next month in Boston. It is a 3-day event 23-25 October.
Details, including costs, can be found on the VMS Software main website.
https://vmssoftware.com/
On 9/6/2024 2:54 PM, William Cox wrote:
I have't seen any mention here about the VMS Software Bootcamp coming up
next month in Boston. It is a 3-day event 23-25 October.
Details, including costs, can be found on the VMS Software main website.
https://vmssoftware.com/
They have now published the agenda:
https://events.vmssoftware.com/bootcamp-2024/agenda
On 2024-09-13, Arne Vajhøj <arne@vajhoej.dk> wrote:
On 9/6/2024 2:54 PM, William Cox wrote:
I have't seen any mention here about the VMS Software Bootcamp coming up >>> next month in Boston. It is a 3-day event 23-25 October.
Details, including costs, can be found on the VMS Software main website. >>>
https://vmssoftware.com/
They have now published the agenda:
https://events.vmssoftware.com/bootcamp-2024/agenda
"Structured DCL Scripting". Hmmm... :-)
BTW, it's 12pm, not 12am (unless you really are having a 13-hour
lunch break). :-)
On 9/13/2024 1:56 PM, Simon Clubley wrote:
On 2024-09-13, Arne Vajhøj <arne@vajhoej.dk> wrote:
On 9/6/2024 2:54 PM, William Cox wrote:
I have't seen any mention here about the VMS Software Bootcamp
coming up
next month in Boston. It is a 3-day event 23-25 October.
Details, including costs, can be found on the VMS Software main
website.
https://vmssoftware.com/
They have now published the agenda:
https://events.vmssoftware.com/bootcamp-2024/agenda
"Structured DCL Scripting". Hmmm... :-)
BTW, it's 12pm, not 12am (unless you really are having a 13-hour
lunch break). :-)
I think it should actually be 12m
https://www.rmg.co.uk/stories/topics/noon-12-am-or-12-pm
What does am and pm mean?
The 12-hour clock divides the 24-hour day into two periods.
   am stands for the Latin ante meridiem, translating to "before midday". This is the time before noon.
   pm stands for post meridiem or "after midday" – the time after noon.
Noon is therefore neither 'ante' (am) nor 'post' (pm) meridiem. Midnight
is also neither am nor pm.
On 2024-09-13, Arne Vajhøj <arne@vajhoej.dk> wrote:
They have now published the agenda:
https://events.vmssoftware.com/bootcamp-2024/agenda
"Structured DCL Scripting". Hmmm... :-)
On Fri, 13 Sep 2024 20:02:20 -0400, Arne Vajhøj wrote:
But one can do some things:
* split logic up in subroutines
Does it have subroutine-local variables?
* have a convention for how to simulate arrays
I remember doing that with clever string substitution. ;)
But one can do some things:
* split logic up in subroutines
* have a convention for how to simulate arrays
On Fri, 13 Sep 2024 20:02:20 -0400, Arne Vajhøj wrote:
But one can do some things:
* split logic up in subroutines
Does it have subroutine-local variables?
The tradition is either to use noon or midnight, or use a 24 hour clock!
On 2024-09-13, Chris Townley <news@cct-net.co.uk> wrote:
The tradition is either to use noon or midnight, or use a 24 hour clock!
I must admit I was a bit surprised to see it written in the way it was
as I am much more used to a 24-hour clock. I don't know if that's more
of a European thing than a US thing however.
On 9/16/2024 8:23 AM, Simon Clubley wrote:
On 2024-09-13, Chris Townley <news@cct-net.co.uk> wrote:
The tradition is either to use noon or midnight, or use a 24 hour clock!
I must admit I was a bit surprised to see it written in the way it was
as I am much more used to a 24-hour clock. I don't know if that's more
of a European thing than a US thing however.
I believe Europe has mostly moved from 12 hour clock to 24 hour clock.
US is commonly 12 hour clock. Except in military and medical worlds.
So a meeting get arranged for 8:00 AM US west coast = 11:00 AM
US east code = 17:00 central Europe.
Arne
I must admit I was a bit surprised to see it written in the way it was
as I am much more used to a 24-hour clock. I don't know if that's more
of a European thing than a US thing however.
I must admit I was a bit surprised to see it written in the way it was
as I am much more used to a 24-hour clock. I don't know if that's more
of a European thing than a US thing however.
I was quite disappointed to see it written that way. VMS has always
used 24 hour time, and the traditional DECUS US agendas were also listed
that way, with sessions starting at 08:00 and some days ending at 23:00.
The traditional VMS time text format is pretty good. Very difficult to misunderstand.
Of course in most programming languages today you can specify the format
to use.
On Tue, 17 Sep 2024 19:06:21 -0400, Arne Vajhøj wrote:
Of course in most programming languages today you can specify the format
to use.
I would say Java in particular is an example of how not to do it.
On 9/17/2024 7:25 PM, Lawrence D'Oliveiro wrote:
I would say Java in particular is an example of how not to do it.
You mean that "HH:mm" and "hh:mm a" are way worse than '%H:%M' and
'%I:%M %p' ?
:-)
On 9/17/2024 3:42 PM, Tom Wade wrote:
I must admit I was a bit surprised to see it written in the way it was
as I am much more used to a 24-hour clock. I don't know if that's more
of a European thing than a US thing however.
I was quite disappointed to see it written that way. VMS has always
used 24 hour time, and the traditional DECUS US agendas were also
listed that way, with sessions starting at 08:00 and some days ending
at 23:00.
The traditional VMS time text format is pretty good. Very difficult
to misunderstand.
Of course in most programming languages today you can specify
the format to use.
$ show time
 17-SEP-2024 19:03:14
$ type now.groovy
import java.text.*
df1 = new SimpleDateFormat("HH:mm")
df2 = new SimpleDateFormat("hh:mm a")
now = new Date()
println(df1.format(now))
println(df2.format(now))
$ groovy now.groovy
19:03
07:03 PM
$ type now.py
from time import *
now = time()
print(strftime('%H:%M', localtime(now)))
print(strftime('%I:%M %p', localtime(now)))
$ python now.py
19:03
07:03 PM
On Tue, 17 Sep 2024 19:40:07 -0400, Arne Vajhøj wrote:
On 9/17/2024 7:25 PM, Lawrence D'Oliveiro wrote:
I would say Java in particular is an example of how not to do it.
You mean that "HH:mm" and "hh:mm a" are way worse than '%H:%M' and
'%I:%M %p' ?
:-)
I mean, look at the mess of classes that makes up the Java date/time API.
The old stuff is pretty straightforward.
On Tue, 17 Sep 2024 21:02:12 -0400, Arne Vajhøj wrote:
The old stuff is pretty straightforward.
All I know is, when I looked at it some years ago, there was a class
*every single method of which is deprecated*. I assumed that class was no longer useful, until I found it referenced all over the place in newer API calls.
It took a while for me to realize: all the original methods of that class were not useful any more, but the class itself was still being created/ manipulated via methods in the newer classes.
On 9/18/2024 9:21 AM, Tom Wade wrote:yyyy
On 2024-09-18 00:25, Lawrence D'Oliveiro wrote:
But it’s not ISO 8601.
Very true, but better than the AM/PM stuff, and unambiguous (unlike
mm/ dd/yy or dd/mm/yy).
yyyy-mm-dd has better characteristics (sorting), but dd-mmm-yyy tend to
be more readable.
On 2024-09-18 00:25, Lawrence D'Oliveiro wrote:
But it’s not ISO 8601.
Very true, but better than the AM/PM stuff, and unambiguous (unlike mm/
dd/yy or dd/mm/yy).
I'm a great believer in ISO 8601 ever since we had a software license
expire on February 2nd when we were expecting it to last till March 3rd!
But it’s not ISO 8601.
On 2024-09-18 00:25, Lawrence D'Oliveiro wrote:
But it?s not ISO 8601.
Very true, but better than the AM/PM stuff, and unambiguous (unlike
mm/dd/yy or dd/mm/yy).
I'm a great believer in ISO 8601 ever since we had a software license
expire on February 2nd when we were expecting it to last till March 3rd!
February 3rd and March 2nd??
On 2024-09-18, Tom Wade <nospam@void.blackhole.mx> wrote:
On 2024-09-18 00:25, Lawrence D'Oliveiro wrote:
But it?s not ISO 8601.
Very true, but better than the AM/PM stuff, and unambiguous (unlike
mm/dd/yy or dd/mm/yy).
VMS date/time formats are much more readable, but the main problem with
VMS timekeeping is that it doesn't have a local timezone offset from a base GMT/UTC timepoint built into it.
Unix got this right and VMS did not.
On 9/19/2024 8:22 AM, Simon Clubley wrote:
On 2024-09-18, Tom Wade <nospam@void.blackhole.mx> wrote:
On 2024-09-18 00:25, Lawrence D'Oliveiro wrote:
But it?s not ISO 8601.
Very true, but better than the AM/PM stuff, and unambiguous (unlike
mm/dd/yy or dd/mm/yy).
VMS date/time formats are much more readable, but the main problem with
VMS timekeeping is that it doesn't have a local timezone offset from a base >> GMT/UTC timepoint built into it.
What is SYS$TIMEZONE_DIFFERENTIAL then?
On 2024-09-24, Arne Vajhøj <arne@vajhoej.dk> wrote:
On 9/19/2024 8:22 AM, Simon Clubley wrote:
On 2024-09-18, Tom Wade <nospam@void.blackhole.mx> wrote:
On 2024-09-18 00:25, Lawrence D'Oliveiro wrote:
But it?s not ISO 8601.
Very true, but better than the AM/PM stuff, and unambiguous (unlike
mm/dd/yy or dd/mm/yy).
VMS date/time formats are much more readable, but the main problem with
VMS timekeeping is that it doesn't have a local timezone offset from a base >>> GMT/UTC timepoint built into it.
What is SYS$TIMEZONE_DIFFERENTIAL then?
A joke. At least when compared to Unix.
VMS commands have no support for showing the active timezone.
Compare the output of the Linux date command with $ SHOW TIME.
In Unix, all timestamps are based on GMT/UTC and the user's timezone is
just an attribute of the user's process, which is the system timezone by default but can be changed by the user. Different processes can have different timezones and none of this affects what timestamp is actually written to the filesystem when the file changes.
Compare the output of the Linux "ls --full" command with $ DIR/FULL.
Note out the Linux command shows the timezone, and note how the timezone changes for each file depending on whether DST was active or not when the file was last modified.
On 9/19/2024 8:22 AM, Simon Clubley wrote:
VMS date/time formats are much more readable, but the main problem with
VMS timekeeping is that it doesn't have a local timezone offset from a
base GMT/UTC timepoint built into it.
What is SYS$TIMEZONE_DIFFERENTIAL then?
Unix got this right and VMS did not.
VMS did not get it right in 1978 - VMS got it almost right in 1993.
On 9/6/2024 2:54 PM, William Cox wrote:
I have't seen any mention here about the VMS Software Bootcamp coming up
next month in Boston. It is a 3-day event 23-25 October.
Details, including costs, can be found on the VMS Software main website.
https://vmssoftware.com/
They have now published the agenda:
https://events.vmssoftware.com/bootcamp-2024/agenda
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 437 |
Nodes: | 16 (2 / 14) |
Uptime: | 193:31:48 |
Calls: | 9,135 |
Calls today: | 2 |
Files: | 13,432 |
Messages: | 6,035,422 |