ruby.git/prism/util/pm_string.c, branch v4.0.2

[ruby/prism] Fix dangling pointers on Windows as well

2025-09-19T14:27:00+00:00

Share the empty source string in `pm_string_mapped_init` and
`pm_string_file_init`.

https://github.com/ruby/prism/commit/f7a9a03a92

Fix dangling pointers

2025-09-13T08:10:44+00:00

[ruby/prism] Fix a possible leak of a file descriptor

2024-11-28T02:15:25+00:00

When mmap fails for any reason, the fd must be closed.

Coverity Scan found this issue.

https://github.com/ruby/prism/commit/c06e9c400f

[ruby/prism] Stat file first to check directory

2024-09-13T19:30:57+00:00

https://github.com/ruby/prism/commit/4ed7de537b

[ruby/prism] Check errno for parsing directory

2024-09-12T17:43:04+00:00

https://github.com/ruby/prism/commit/d68ea29d04

[ruby/prism] UTF-8 characters in file name

2024-09-11T19:17:12+00:00

https://github.com/ruby/prism/commit/487f0ffe78

[ruby/prism] Parse tempfile

2024-09-11T15:39:22+00:00

https://github.com/ruby/prism/commit/31154a389a

[ruby/prism] Add explicit check for PRISM_HAS_NO_FILESYSTEM

2024-07-26T17:07:50+00:00

https://github.com/ruby/prism/commit/89c22f0e6c

[ruby/prism] Fallback to pm_string_file_init on platforms without memory-mapped files

2024-07-26T17:07:50+00:00

> ..., and on other POSIX systems we'll use `read`.

As `pm_string_mapped_init`'s doc comment says, it should fall back to
`read(2)`-based implementation on platforms without memory-mapped files
like WASI, but it didn't. This commit fixes it by calling `pm_string_file_init`
in the fallback case.
Also `defined(_POSIX_MAPPED_FILES)` check for `read(2)`-based path is
unnecessary, and it prevents the fallback from being executed, so this
change removes it.

https://github.com/ruby/prism/commit/b3d9064b71

[PRISM] Ensure not opening directories

2024-07-18T17:03:25+00:00