I'm not convinced that any automatic memory management scheme
will buy much with real time applications. Generally with
real-time processes, you need to pre-allocate. I think GC could
be feasible for a real-time application if the GC is precise and
collections are scheduled, instead of run randomly. Scoped memory
also helps.
- Re: DIP60: @nogc attribute Walter Bright via Digitalmars-d
- Re: DIP60: @nogc attribute via Digitalmars-d
- Re: DIP60: @nogc attribute Andrei Alexandrescu via Digitalmars-d
- Re: DIP60: @nogc attribute Walter Bright via Digitalmars-d
- Re: DIP60: @nogc attribute Manu via Digitalmars-d
- Re: DIP60: @nogc attribute via Digitalmars-d
- Re: DIP60: @nogc attribute Manu via Digitalmars-d
- Re: DIP60: @nogc attribute via Digitalmars-d
- Re: DIP60: @nogc attribute Walter Bright via Digitalmars-d
- Re: DIP60: @nogc attribute Manu via Digitalmars-d
- Re: DIP60: @nogc attribute w0rp via Digitalmars-d
- Re: DIP60: @nogc attribute Byron via Digitalmars-d
- Re: DIP60: @nogc attribute Brad Anderson via Digitalmars-d
- Re: DIP60: @nogc attribute Byron via Digitalmars-d
- Re: DIP60: @nogc attribute Jacob Carlborg via Digitalmars-d
- Re: DIP60: @nogc attribute bearophile via Digitalmars-d
- Re: DIP60: @nogc attribute Jacob Carlborg via Digitalmars-d
- Re: DIP60: @nogc attribute Tobias Pankrath via Digitalmars-d
- Re: DIP60: @nogc attribute monarch_dodra via Digitalmars-d
- Re: DIP60: @nogc attribute monarch_dodra via Digitalmars-d
- Re: DIP60: @nogc attribute Jacob Carlborg via Digitalmars-d