The Racket repository
978d60e4a7
Some synchronization built into `close-output-port` seems unnecessary on modern Windows (NT and up). An extra manager thread is needed for a anonymous pipe for "write ready?" purposes, but not to buffer output. The Windows documentation is not entirely clear on this point, but experiments suggest that modern anonymous pipes behave in the obvious way. Meanwhile, adjust the io layer used by Racket CS with the synchronization that would be needed for Windows 95. This adjustment is questionable, because it doesn't seem likely that we'll ever go back that far with Racket CS. But the rktio interface to support flushing synchronization might somehow be needed in a future setting, or mabe it will turn out that I'm wrong about pipe buffers. |
||
|---|---|---|
| .github | ||
| .gitlab | ||
| pkgs | ||
| racket | ||
| .gitattributes | ||
| .gitignore | ||
| .gitlab-ci.yml | ||
| .mailmap | ||
| .travis.yml | ||
| appveyor.yml | ||
| azure-pipelines.yml | ||
| CONTRIBUTING.md | ||
| INSTALL.txt | ||
| LICENSE-APACHE.txt | ||
| LICENSE-MIT.txt | ||
| LICENSE.txt | ||
| Makefile | ||
| README.md | ||
This is the source code for the core of Racket. See "INSTALL.txt" for full information on building Racket.
To build the full Racket distribution from this repository, run make
in the top-level directory. To build minimal Racket, run make base.
The rest of the Racket distribution source code is in other repositories, mostly under the Racket GitHub organization.
Contribute to Racket by submitting a pull request, joining the development mailing list, or visiting the IRC or Slack channels.
Racket is free software; see "COPYRIGHT" and "CONTRIBUTING.md" for more details.