[#109207] [Ruby master Feature#18915] New error class: NotImplementedYetError or scope change for NotImplementedYet — Quintasan <noreply@...>
Issue #18915 has been reported by Quintasan (Michał Zając).
18 messages
2022/07/14
[ruby-core:109236] [Ruby master Bug#18924] lstrlen and lstrcat still in use
From:
"test35965@... (Alexander Riccio)" <noreply@...>
Date:
2022-07-17 20:42:52 UTC
List:
ruby-core #109236
Issue #18924 has been reported by test35965@gmail.com (Alexander Riccio). ---------------------------------------- Bug #18924: lstrlen and lstrcat still in use https://bugs.ruby-lang.org/issues/18924 * Author: test35965@gmail.com (Alexander Riccio) * Status: Open * Priority: Normal * Backport: 2.7: UNKNOWN, 3.0: UNKNOWN, 3.1: UNKNOWN ---------------------------------------- In practice, as-used, this is probably benign, but is a Terrible Idea. There are several places where someone's still using lstrcat and lstrlen in ruby. lstrcat catches and ***suppresses*** access violations. I have been burned by this in the wild as a user of other software, corrupting data and causing mysterious crashes. There's no good reason to use these functions. IIRC, they may even date back to before the standard library was standard (on windows?)? Swapping them for standard functions like strcpy is not great, but can only break code that was incorrect and memory-corrupting already. -- https://bugs.ruby-lang.org/ Unsubscribe: <mailto:ruby-core-request@ruby-lang.org?subject=unsubscribe> <http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>