Difference between revisions of "VMS Python compatibility issues"
m |
m |
||
Line 35: | Line 35: | ||
##<code>strftime()</code> | ##<code>strftime()</code> | ||
##*Does not support <code>%G</code> format | ##*Does not support <code>%G</code> format | ||
− | ##*Exhibits undefined behavior when format ends with <code> | + | ##*Exhibits undefined behavior when format ends with <code>%</code> |
− | ##*<code> | + | ##*<code>%4Y</code> is padded with spaces |
#Miscellaneous | #Miscellaneous | ||
##Environment variables have unusual implementation - through logical names. There is no appropriate way to get all environment variables. | ##Environment variables have unusual implementation - through logical names. There is no appropriate way to get all environment variables. | ||
− | ##OpenVMS sqlite3 port does not support "OR ROLLBACK" | + | ##The OpenVMS sqlite3 port does not support "OR ROLLBACK" |
##Program prints crush dump | ##Program prints crush dump | ||
##<code>locale.strxfrm()</code> works unusual | ##<code>locale.strxfrm()</code> works unusual |
Revision as of 00:42, 13 September 2020
- File system
- Directories and files with the same name are allowed
- Files have versioning, therefore two files with the same name might have different content
- Shared stream I/O does not work
- To guarantee the file content is on the disk the
fsync()
function must be used - Because files can be referenced using logical names the real file path may be different from the “path” used to open a file
- Files has no access time attribute
- Changing a files permissions also changes its modification time
- Changing the content of a directory does not change the directory modification time.
- Files have four rights bits (read, write, execute, and delete); Linux (UNIX) has only three (read, write, and execute)
- The ‘.DIR’ extension is reserved
- Non-blocking file IO is not supported by the OpenVMS CRTL
- There are various known issues with symbolic link implementation
- The symbol '$' is commonly used in file and directory names
- On OpenVMS chmod(0) sets the user's default permissions as opposed to resetting permissions
- To delete a directory the user has to have ‘delete’ permission for the directory
- On OpenVMS
mkdir()
creates all intermediate directories (if required)
- Process
- There are no Linux-like
fork()
andspawn()
functions - Pipes are created via mailbox and are not totally compatible with UNIX pipes (compatibility issues)
- If a child process has threads, each thread posts 'END-OF-PIPE' when the child completes/terminates
- The functions
select()
andpoll()
work only with sockets - The function
siginterrupt()
is not supported - Numerous compatibility issues with signals
- Interrupting I/O operations may cause the process to hang
- There is no root user with zero UID
- Processes do not handle recursion overflow cleanly
- There are no Linux-like
- Sockets
AF_UNIX
has different meaning- Binding socket to empty address fails (wildcard resolved to multiple address).
getpeername()
returns ‘0.0.0.0’ instead of error- OpenVMS crashed on
socket.socket.sendall
- Time
time_t
is unsignedstrftime()
- Does not support
%G
format - Exhibits undefined behavior when format ends with
%
%4Y
is padded with spaces
- Does not support
- Miscellaneous
- Environment variables have unusual implementation - through logical names. There is no appropriate way to get all environment variables.
- The OpenVMS sqlite3 port does not support "OR ROLLBACK"
- Program prints crush dump
locale.strxfrm()
works unusual
- Compiler
uint_ptr
is always 64 bit, void* is 32 bit or 64 bit- Compiler does not support relative include paths