News for hackers. Stuff that matters.
Re:Cello – High Level C by noncoml on Monday January 20, 2020 @06:29PM (#22102947)
Just my opinion, don't mean to be inflammatory, but if the user has to know and manually manage stack vs heap objects, then I wouldn't call it "High Level" language.
Re:Cello – High Level C by pmiller2 on Monday January 20, 2020 @06:39PM (#22102996)
Then just allocate everything on the stack and use the optional garbage collector: http://libcello.org/learn/garbage-collection
Re:Cello – High Level C by jessaustin on Monday January 20, 2020 @09:50PM (#22103939)
Allocating on the stack doesn't need GC.
Re:Cello – High Level C by pmiller2 on Monday January 20, 2020 @10:39PM (#22104131)
No, but it makes it easier (more “high level”) when you don’t need to explicitly deallocate things, ever.
Re:Cello – High Level C by zozbot234 on Monday January 20, 2020 @06:35PM (#22102976)
That raises a question, would you call C# a "High Level" language?
Re:Cello – High Level C by rubber_duck on Monday January 20, 2020 @06:43PM (#22103025)
In C# it's more relevant to understand semantics (ref/value type) than allocation details (unless you actually care about low level details for performance/interop)
Re:Cello – High Level C by nobleach on Monday January 20, 2020 @06:49PM (#22103057)
I'd say the fact that structs are stack-allocated, and you can slip right through years of development without even knowing that fact... yeah, it's pretty high-level. C# doesn't have `malloc`. .Net apps are managed, so all of those low-level things one has to/gets to do are abstracted away.