Skip Navigation
Removed
Question about 'Design Concepts in Programming Languages' -- 3 Types of Semantics, what do the mean?
  • ++A; thanks! So, in a domain-specific language, like ASDL which I implemented, it's mostly the denotational semantics at work, but in a GPL like C, it's mostly operational. Am I right?

    btw if you got the time, could you pls explain axiomatic semantics, that would be great. I don't at all understand this one. Thanks.

  • Removed
    Mini-computers capped out too soon man. I hate miniaturization! Make computers big again!
  • This statement is completely wrong. Like, to a baffling degree. It kinda makes me wonder if you’re trolling.

    No I just struggle at getting my meaning across + these stuff are new to me. What I meant was 'Go does memory management LIKE a VM does'. Like 'baking in the GC'. Does that make sense? Or am I still wrong?

  • Removed
    Rust's denotational semantics make memory safety possible!
  • @Ferk @FizzyOrange @posgamer @reflectedodds @ExperimentalGuy: There are errors in what I said. I admit I am not an expert. I will come back with better explanations for my stance, after I have read more about it.

  • Removed
    Rust's denotational semantics make memory safety possible!
  • First off, I apologize if I did not add a disclaimer saying I could be wrong. But given this, what is exactly the difference between denotaional and operational semantics? I base what I said on [my understanding of books about language theory. But it seems like I got the wrong gist. Where do you recommend I start?

    PS: I'll add a void to the post rn.

  • Removed
    Mini-computers capped out too soon man. I hate miniaturization! Make computers big again!
  • I know about all this --- I actually began implementing my own JVM language a few days ago. I know Android uses Dalvik btw. But I guess a lot of people can use this info; infodump is always good. I do that.

    btw I actually have messed around with libgcc-jit and I think at least on x86, it makes zero difference. I once did a test:

    -- Find /e/ with MAWK -> 0.9s -- Find /e/ with JAWK -> 50s.

    No shit! It's seriously slow.

    Now compare this with go-awk: 19s.

    Go has reference counting and heap etc, basically a 'compiled VM'. I think if you want fast code, ditch runtime.

  • InitialsDiceBearhttps://github.com/dicebear/dicebearhttps://creativecommons.org/publicdomain/zero/1.0/„Initials” (https://github.com/dicebear/dicebear) by „DiceBear”, licensed under „CC0 1.0” (https://creativecommons.org/publicdomain/zero/1.0/)CH
    ChubakPDP11+TakeWithGrainOfSalt @programming.dev
    Posts 0
    Comments 0