[Mono-devel-list] How to handle huge string collation resources?

[Miguel de Icaza]

Hello,

> > BTW doesn't that mean all that kind of culture resources had better
> > become managed resources, unless they are required at runtime?
> > We also have huge culture-info-table.h and char-conversions.h
> > in metadata.
> 
> They are in C, where they are a const array. One advantage of having
> them there is that we don't have to do conversions for different endian
> systems.

Cant the same be said about the table that Atsushi is creating?  Do we
really worry about the 200k replicated between Mono and libmono.so.

And the libmono.a is only shipped to those developing. 

The resource approach has also the downside that access to it would be
through the Stream interface (even if mmapped) while getting a pointer
to a C-statically defined array would allow the corlib code to access it
without any wrapper code.

Both approaches enjoy the mmap benefits.

Miguel.