Show HN: Crown – A flexible game engine written from scratch in C++

Post by mikepurvis » Thu, Jun 22, 2017, 1:24 PM UTC

dbartolini wrote: post #80

mikepurvis wrote: post #79

Earlier quoted context omitted.

Huh. Okay, that was not immediately apparent from viewing the project— it looked like a hand-written Makefile. Link for the curious: https://github.com/bkaradzic/GENie Appreciating that CMake has its warts, it also has a ton of mindshare and has lots of convenient modules for handling common dependencies. What are the motivations to use a Lua-based scheme instead?

I find GENie/premake way simpler to read and write. Also, you have more flexibility since your build scripts have full-fledged Lua capabilities.

Post by mikepurvis » Thu, Jun 22, 2017, 1:29 PM UTC

dbartolini wrote: post #80

mikepurvis wrote: post #79

Earlier quoted context omitted.

Huh. Okay, that was not immediately apparent from viewing the project— it looked like a hand-written Makefile. Link for the curious: https://github.com/bkaradzic/GENie Appreciating that CMake has its warts, it also has a ton of mindshare and has lots of convenient modules for handling common dependencies. What are the motivations to use a Lua-based scheme instead?

I find GENie/premake way simpler to read and write. Also, you have more flexibility since your build scripts have full-fledged Lua capabilities.

Post by zakirenish » Thu, Jun 22, 2017, 1:41 PM UTC

typon wrote: post #83

zakirenish wrote: post #55

If you come to finance, most of the developers love premature templatization, it makes them feel like they know something. Not sure it that can be attributed to their insecurity about C++ coding skills, but it gets really ridiculous at times.

What's wrong with using templates vigorously?

Post by bascule » Thu, Jun 22, 2017, 1:46 PM UTC

cpfohl wrote: post #69

dkersten wrote: post #25

Earlier quoted context omitted.

sane like Go Yet Go uses the oh-so-error-prone return value error checking that has been so successful in C :/

Disclaimer: Not a go apologist, I admire it, but don't use it. With Go you get a compiler error if you don't do something with that error. You have to explicitly decide to ignore it with `_`. As far as I remember that's quite different from C where you can get an error code, ignore it, and never realize you've missed it.

    import "os"

    func main() {
	    os.Open("this file does not exist")
    }

    use std::fs::File;

    fn main() {
        File::open("this file does not exist");
    }

    warning: unused result which must be used
      --> test.rs:14:5
       |
    14 |     File::open("this file does not exist");
       |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
       |
       = note: #[warn(unused_must_use)] on by default

Post by agentultra » Thu, Jun 22, 2017, 2:06 PM UTC

badsectoracula wrote: post #10

comstock wrote: post #2

Interesting! I'd be interested in better understanding the motivation behind Orthodox C++. In particular, you seem to dump most of the C++ standard library: "Don't use anything from STL that allocates memory, unless you don't care about memory management." I now mostly avoid templatization in my own code unless there's a really good reason. But the standard library often lets me avoid explicit memory allocation. Woul…

Generally speaking many C++ game engines avoid the STL stuff and reimplement their own more predictable containers, often with custom allocation schemes. The engine at the last game company i worked at, for example, had its own containers and memory allocator and allowed you to define the allocation category and pool per allocator and per object class (so, e.g., dynamic strings would be isolated to their own pool to…