Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

As proven by Oberon, it can be made with unmodified Go as well.

What it would be missing, and was fixed in Active Oberon, is explicit support for untraced references.



> untraced references

could you explain that a little more. Are references in Oberon bidirectional? Meaning there is a list of every reference ever taken and by whom?


Common GC speak.

Traced references are tracked by whatever form the language offers automatic memory management.

Untraced references are a kind of safe pointers, basically the memory they point to isn't tracked by the GC/RC infrastructure and they are managed in some form of manual memory management, and can be used as part of unsafe code for pointer arithmetic.

The languages then provide means of converting between both worlds, naturally it always requires making use of some form of unsafe code block.


Ok, got it. Off GC Heap memory allocations.

I thought it might be an Oberon specific concept. I'd like to see something like ref counting, but an actual ref list where there is a global list of references to an object.




Consider applying for YC's Winter 2026 batch! Applications are open till Nov 10

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: