5 ms·

The comment was about error handling syntax, not constant declaration syntax. The comparison being made is between `result = foo(); if (!result) { ... }`, `foo(

by Rusky 9y ago

The comment was about error handling syntax, not constant declaration syntax. The comparison being made is between `result = foo(); if (!result) { ... }`, `foo();`, and `foo()?;`. > And for real low level to the metal systems programming, everything is unsafe; so you may as well be writing in C. Sounds wrong to me. People have done things like booting up x86 with all of the hardware bit-twiddling behind safe interfaces (for example: https://os.phil-opp.com/ https://os.phil-opp.com/).

CalChris 9y ago
setjmp wasn't even supported. I had to use an LLVM intrinsic. This only barely worked if I put the setjmp and the longjmp in separate files.
- Rusky 9y ago
  Why is setjmp such a major issue for you? It's a C language feature, not a "real low level to the metal systems programming" requirement.
  - CalChris 9y ago
    If you are calling C or assembly and there is any sort of processor exception, you need to establish a signal() handler and you will need setjmp/longjmp to re-establish a safe stack frame. Yes, this is a C/assembly thing. But it is also a Linux/BSD/Unix thing. You really cannot call Rust a systems programming language if signal/setjmp/longjmp are not fully supported. It just goes with the territory.
    - Rusky 9y ago
      Linux/BSD/Unix are hardly the only systems programming environments. I'd hesitate even to call them the majority. And for now, there are definitely ways to handle signals using libraries.
      - lossolo 9y ago
        > Linux/BSD/Unix are hardly the only systems programming environments. I'd hesitate even to call them the majority. Do you have any source that can confirm that? Because what you wrote seems really wrong. I see linuxes/bsd/unix EVERYWHERE (Android/iOS/OSX/almost all backend servers etc.)
        Rusky 9y ago
        I'm thinking of embedded systems and desktop machines- the first tends not to use an OS nearly that big (if any at all), and the second tends to use Windows.

by Rusky 9y ago

CalChris 9y ago

setjmp wasn't even supported. I had to use an LLVM intrinsic. This only barely worked if I put the setjmp and the longjmp in separate files.

Rusky 9y ago
Why is setjmp such a major issue for you? It's a C language feature, not a "real low level to the metal systems programming" requirement.
- CalChris 9y ago
  If you are calling C or assembly and there is any sort of processor exception, you need to establish a signal() handler and you will need setjmp/longjmp to re-establish a safe stack frame. Yes, this is a C/assembly thing. But it is also a Linux/BSD/Unix thing. You really cannot call Rust a systems programming language if signal/setjmp/longjmp are not fully supported. It just goes with the territory.
  - Rusky 9y ago
    Linux/BSD/Unix are hardly the only systems programming environments. I'd hesitate even to call them the majority. And for now, there are definitely ways to handle signals using libraries.
    - lossolo 9y ago
      > Linux/BSD/Unix are hardly the only systems programming environments. I'd hesitate even to call them the majority. Do you have any source that can confirm that? Because what you wrote seems really wrong. I see linuxes/bsd/unix EVERYWHERE (Android/iOS/OSX/almost all backend servers etc.)
      - Rusky 9y ago
        I'm thinking of embedded systems and desktop machines- the first tends not to use an OS nearly that big (if any at all), and the second tends to use Windows.