• 0 Posts
  • 2 Comments
Joined 1 year ago
cake
Cake day: June 10th, 2023

help-circle
  • shami1kemi1@sopuli.xyztoProgrammer Humor@programming.devWhitespace
    link
    fedilink
    arrow-up
    16
    arrow-down
    1
    ·
    5 months ago

    Then again, at least in C, the mantra is “declaration follows usage”. Surely you don’t write pointer dereferences as * ptr? Most likely not, you most likely write it as *ptr. The idea behind the int *ptr; syntax is basically that when you do *ptr, you get an int.

    And with this idea, stuff like function pointers (int (*f)(void)), arrays of pointers (int *a[10]) versus pointers of arrays (int (*a)[10]) etc. start making sense. It’s certainly not the best way to design the syntax, and I’m as much a fan of the Pascal-styled “type follows the identifier” syntax (e.g. let x: number;) as anyone, but the C way does have a rhyme and a reason for the way it is.


  • Why Emacs has sound support? Well, you could ask that about many other things in Emacs, but sound support is relatively understandable since you want to be able to do things such as play notification sounds. That’s for example how erc recommends the use of the sound system.

    As to why ALSA and not PipeWire, well, for one, the support is from before pipewire was even a thing. The ALSA support even seems to be from the time when PulseAudio was new (2006 seems to be year of the first ALSA-related commits in src/sound.c.) And since it seems to work, I’m not sure that the developers are that keen to just going and replacing the ALSA support with PipeWire, especially given the latter’s complexity.