pollen/mode reader #88

In mode.rkt I was interested to see that pollen/mode still does a lot of work to make the reader work with Racket 6.0/6.1 because of changes in the at-exp reader that happened in 6.2. @mbutterick do you remember what changed in 6.2? Are there subtle differences in the surface syntax allowed by #lang pollen/mode compared with post-6.2 #lang at-exp (besides the command character)? If not, is all of this still necessary now that Pollen no longer supports anything earlier than 6.3?

In `mode.rkt` I was interested to see that `pollen/mode` still does [a lot of work][1] to make the reader work with Racket 6.0/6.1 because of changes in the at-exp reader that happened in 6.2. @mbutterick do you remember what changed in 6.2? Are there subtle differences in the surface syntax allowed by `#lang pollen/mode` compared with post-6.2 `#lang at-exp` (besides the command character)? If not, is all of this still necessary now that Pollen no longer supports anything earlier than 6.3? [1]: https://github.com/mbutterick/pollen/blob/bd23f651fb4be5e308ce31422dfb2193eff5dae7/pollen/mode.rkt#L3-L15

I don’t remember what specifically changed in 6.2. But yes, judging from that comment it’s safe to amend that file just to import the necessary function from Racket.

I was able to cut a lot of code out of pollen/mode (see 9a838418e7). Maybe it can be cut down farther. But the pieces remaining seem necessary because the at-exp metalanguage wasn’t designed to be customized with a different command character, so a certain amount of copying & pasting seems unavoidable.

I was able to cut a lot of code out of `pollen/mode` (see https://github.com/mbutterick/pollen/commit/9a838418e7c42cc90f1dd9e3e857faf2efb3d8bf). Maybe it can be cut down farther. But the pieces remaining seem necessary because the `at-exp` metalanguage wasn’t designed to be customized with a different command character, so a certain amount of copying & pasting seems unavoidable.

Labels Milestones

pollen/mode reader #88