> Shap wrote >The intent is that String is used for interop. The definition given is weasily enough that almost any underlying encoding can be jiggered into working, which leaves us free to use .Net strings directly (for example).
You are seeing a more fine grained interop and an almost opaque string can wrap / be a .NET string , I was looking more at doing strings the bitc way and sending it to the C or the CLR and then converting to our representation when we get it back. I suppose this comes down to libraries - the fine grained approach allows much better use of the .NET libraries and in fact would make BitC and full .NET language . Which is good and bad. If you want to use CLR strings what about collections , does List<String> fit into the picture ? Ben
_______________________________________________ bitc-dev mailing list [email protected] http://www.coyotos.org/mailman/listinfo/bitc-dev
