Hi - On 5/10/17, 1:46 AM, "Tomsy Paul" <[email protected]> wrote:
>By the way why make spectests not invoked by default in Developer mode? We tend to have a bunch of Makefile rules that are not invoked by default, for one reason or another. In this case I think the spec tests change infrequently enough and the Makefile support we have there only knows how to update all of them, so having 'make' run it would be distracting during normal development. (And besides, we need the release tarball to use the same Makefile and some of these targets use files not in the release). I think the other Makefile rules that might be important but don't run by default are: make test-env -- creates support stuff for start_test make docs --- creates our documentation into RST, HTML make parser -- rebuilds lexer and parser make chplvis -- make chplvis tool Cheers, -michael > > >On Fri, May 5, 2017 at 6:15 PM, Michael Ferguson ><[email protected]> wrote: > >Hi - > >On 5/5/17, 2:04 AM, "Tomsy Paul" <[email protected]> wrote: > >>Hi all, >> >>Since I did not use to update myself with the previous chapel changes >>regularly, I am once again going through the language spec. > > >Are you already familiar with this page: > http://chapel.cray.com/docs/latest/language/evolution.html > >? > >>I refer to Oct. 2016 version. > >I'm surprised you wouldn't use the April 6 version, which should >match our most recent release (1.15). It's available from the >"View Language Specification" link here: > > http://chapel.cray.com/docs/latest/language/spec.html > >>Many sample programs mentioned in Language spec is missing/renamed in the >>examples folder. > >These spec tests are tested nightly and created automatically in >a manner that ensures that they are synchronized with what is >in the language specification. > >If you are using a release version of Chapel, the spec examples >will only match up with the version of the spec at the time of that >release. > >Of course, you should be able to check out the git repository >at any time and get a version of both the spec and the examples. >Note that you have to do `make spectests` to generate the >tests into the examples/spec directory. (If you were originally >using a git checkout, perhaps that is the missing step). > >Cheers, > >-michael > > >>The following are a few to site. >> >>conditionals.chpl >>beginUnordered.chpl >>coforallAndEquivalent.chpl >>cobeginAndEquivalent.chpl >>beginWithSyncVar.chpl >> >> >>singleVar.chpl - replaced with syncsingle.chpl? >>syncCounter.chpl - replaced with syncsingle.chpl? >> >>while.chpl - Contents changed >> >> >> >> > > > > > > > > > > > > ------------------------------------------------------------------------------ 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
