Re: [ros-dev] [ros-diffs] 01/01: [WINLOGON] Clean up part 2 - Replace the UNICODE_STRING usMessage by a PWSTR pszMessage. - Use the "%02d:%02d:%02d" time format and get rid of the safe string printf b

Hey, I'm going to chime in here. If you want to fix this problem: Don't use C! Use C++, C#, Java etc. > instead! > Honestly, this is inane right? ReactOS currently uses C predominantly, but we can't use that as an excuse for shitty code which breaks, crashes, or has buffer overflows. Security is

[ros-dev] R: [ros-diffs] 01/01: [WINLOGON] Clean up part 2 - Replace the UNICODE_STRING usMessage by a PWSTR pszMessage. - Use the "%02d:%02d:%02d" time format and get rid of the safe string printf be

Some people use the very same argument to write OS’s in Rust. It’s not like it doesn’t make sense, it’s just not necessary. If C++ and Rust can compile to safe code, so can C. You just gotta define and abide by sensible safety practices. BR, Riccardo P. Bestetti Da: Ros-dev [mailto:ros-dev-bo

Re: [ros-dev] R: [ros-diffs] 01/01: [WINLOGON] Clean up part 2 - Replace the UNICODE_STRING usMessage by a PWSTR pszMessage. - Use the "%02d:%02d:%02d" time format and get rid of the safe string print

One thing weighs in favour of using C++ over C and that is the increased type checking with the former, whereas the latter is decidedly weakly-typed. That said, C is hardly the maintenance and programming nightmare that it is made out to be by many. Proper design and architecture can make life