Hi Tomsy -- This capability and flag have long since been retired:
https://github.com/chapel-lang/chapel/commit/0dc836f https://github.com/chapel-lang/chapel/commit/6b3879d585f371710262bb115feeb73adfc339e0 Over time, the complexity of having the runtime depend on Chapel code seemed to outweigh the benefit of being able to write runtime code in Chapel, which is why we ended up retiring it. I hadn't realized that they were still mentioned in documentation and will remove them (unless you'd like to contribute a PR to do so yourself). If there was a related capability you needed this for, please let us know. -Brad On Wed, 3 May 2017, Tomsy Paul wrote: > Dear all, > >> From doc/developer/bestPractices/potpourri.txt, in --runtime compiler flag, > I understand that Runtime modules are less used now. > > 1. Could not find runtime/src/common-chpl folder mentioned in potpourri.txt. > > 2. --runtime as a compiler flag resulted in an error. Is it a build flag? > > 3. What is the current status of runtime modules, like ChapelArray.chpl? > ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ Chapel-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/chapel-developers
