You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Could you please confirm that Term::ReadKey is or is not thread-safe?
I experience quite a lot of crashes of Term::ReadKey 2.33 in a forking environment under Windows.
The text was updated successfully, but these errors were encountered:
The module is not designed with thread safety in mind, (it pre-dates threading in Perl and fork emulation on Windows,) so it would be fairly safe to assume it won't play nicely in a threaded environment.
Specifically the XS parts of the module make calls to functions in the system C library which are probably not re-entrant in most implementations, and there are several static "global" variables in the XS code itself that are used to retain state which would also militate against its being "thread-safe"..
While it would be theoretically possible to make a module that does what Term::ReadKey does in a more thread-safe manner, it would almost certainly have to be a new and separate module as it would need a completely different interface style
Could you please confirm that Term::ReadKey is or is not thread-safe?
I experience quite a lot of crashes of Term::ReadKey 2.33 in a forking environment under Windows.
The text was updated successfully, but these errors were encountered: