And Michael Ferguson writes: > Of course, the other way would be to add an optional runtime > layer, like CHPL_REGEXP or CHPL_GMP. That might make sense if > the networking library has other dependencies that might not > always be available, [...]
Related to curl, there's also c-ares: http://c-ares.haxx.se/ Likely could be bundled to avoid any dependencies. > Chapel doesn't have anything like #ifdef, but the generic > programming facility is very flexible and could support string > comparison on config params that indicate the current > platform. I believe that should work now, but havn't tried > it. It does. I need to revisit my atomic goo that uses it at some point. But the CHPL_TARGET_PLATFORM values don't seem terribly well defined. The compiler complains about them internally on Edison (XC30), for example... There always will be a need to specify platform-specific code. Throwing it out to C feels hacky, particularly since that code may be relying on details of the current Chapel->C conversion. -- Jason ------------------------------------------------------------------------------ Rapidly troubleshoot problems before they affect your business. Most IT organizations don't have a clear picture of how application performance affects their revenue. With AppDynamics, you get 100% visibility into your Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro! http://pubads.g.doubleclick.net/gampad/clk?id=84349351&iu=/4140/ostg.clktrk _______________________________________________ Chapel-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/chapel-developers
