On Fri, 07 Oct 2011 03:32:13 +0200, Walter Bright
<[email protected]> wrote:
On 10/6/2011 4:48 PM, Martin Nowak wrote:
Which isn't wanted because of the binary size, right?
It is a substantial size problem. There's also a performance issue - the
gc has to read those tables and iterate in a non-trivial way. For
example, if a struct has an embedded static array of pointers in it,
you'll need a way to embed a loop in the gc scanner.
Sounds like an interpreter :), with the garbage collector interpreting
type infos as bytecode.
As this is also a requirement for precise scanning and runtime type
information
couldn't a heavily compressed format be found for it.
Something not so weird as DWARF but using a mixture of source encoding
and tables to lower redundancy.
Compression has its own problem - performance.
