Is it possible to adjust the reader and/or the expander such that procedure application is allowed only with parentheses, and syntactic forms are allowed with brackets other than parenthesis?

Yes, you can control whether brackets are equivalent to parentheses or not.

read-square-bracket-as-paren

I’m sorry, I’m unsure how I can use that to allow macros to be called with non-parentheses.

Sorry - it only solves the first half. Preventing brackets to be interpreted as applications.

I think that i can solve it with read-square-bracket-with-tag.

Yes, I think so too.

Another possibility is consult the 'paren-shape property: #lang racket/base (require (for-syntax racket/base)) (provide (except-out (all-from-out racket/base) #%app) (rename-out [round-app #%app])) (define-syntax (round-app stx) (syntax-case stx () [(_ . app) (if (eq? (syntax-property #'app 'paren-shape) #\[) (raise-syntax-error #f "bad application" stx) #`(#%app . app))]))

Thanks for the answers! This clears things up.

Any hints for this error? https://www.reddit.com/r/Racket/comments/jmtnuy/drracket_error/

Bump. He has now installed 7.8 on Ubuntu, but has the same problem. Any ideas?

FWIW I cannot reproduce on my Ubuntu running DrRacket 7.8 cs

Do you have the same paths as he has?

for module path: eopl/tests/private/utils collection: "eopl/tests/private" in collection directories: /home/can/.racket/7.8/collects /usr/share/racket/collects ... [309 additional linked and package directories] sub-collection: "tests/private" in parent directories: /usr/share/racket/pkgs/eopl

I do not, but I may be installing Racket atypically.

I am confused by the last lines: drracket install: package is currently installed in a wider scope package: eopl installed scope: installation given scope: user

I do a unix style install into /usr/local/stow/racket-$RACKET_VERSION and then use GNU stow to manage links and such so I can switch between versions semi-easily.

eopl is in the base install so that’s what you see if you try to raco pkg install eopl

Question is - Is the test directory always installed?

Yeah, it should be. The package hasn’t got a -doc, -test or similar.