[Info-vax] scp or sftp: file is "raw", needs to be parsed - possible to work around that?

[Craig A. Berry]

On 5/20/21 11:30 AM, Stephen Hoffman wrote:
> On 2021-05-20 15:53:33 +0000, Craig A. Berry said:
> 
>> On 5/20/21 9:54 AM, Stephen Hoffman wrote:
>>
>>> https://groups.google.com/g/comp.os.vms/c/dhUzZ7HifPo/m/QIVOhPuwAgAJ
>>
>>> That there are (were?) reportedly ~eight different stat() 
>>> implementations/behaviors around was news to me, and sounds like a 
>>> bug farm, too.
>>
>> And last time I checked none of them implements the timestamps as 
>> struct timespec as required by POSIX since 2008 rather than time_t.
> 
> AFAICT and with the exception of POSIX threads 1003.1-1996, VSI claims 
> no compliance with any of the POSIX or Single UNIX Specification 
> standards. So there's that.

Right.  Although it might be surprising to some people that compiling
with /DEFINE=(_USE_STD_STAT=1) gives you a stat struct that conforms to
an older standard rather than any recent one.  And it's still a
portability problem.

> https://vmssoftware.com/docs/VSI_OVMS_SPDQS_OS_V842L1I_UPD1.pdf
> https://vmssoftware.com/docs/VSI_C_spd.pdf

The SPD for C doesn't say much about the CRTL other than you need to
have it to use C.  The CRTL appears not to have its own SPD and if the
release notes for last year's C99 patch are available anywhere public, I
couldn't find them.

> The next related upgrade past the recently-added C99 support will be 
> with the Clang port for OpenVMS on x86-64.

CRTL changes and the clang++ port seem orthogonal to me -- I don't see
them getting a new CRTL written in time for the C++ release that is
supposed to happen this quarter (or even if that slips by a quarter or two).

> Ah, and I hadn't noticed that single-host shared stream I/O is on the 
> roadmap. The native compilers are all arriving 2021H2; somewhere between 
> V9.1 and V9.2.

It's there, and so is the PostgreSQL database that depends on it.