Hi Brad - Thanks for your response. Answering one question:
>To that end, my question would be what it is about >'c_ptr' that wants to preserve names and to try and make that case the >exception rather than the rule. It's really just that C compilers emit warnings when you do things with different but equivalent pointer types. For example, if I pass int8_t* into a routine expecting char*, I usually will get a warning. And we don't like our generated code giving us warnings... I suppose we could ask the C compilers for fewer warnings. -michael ------------------------------------------------------------------------------ Dive into the World of Parallel Programming The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net/ _______________________________________________ Chapel-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/chapel-developers
