Lan­guage-ori­ent­ed Pro­gram­ming in Rack­et

Rack­et’s more than just a bat­ter­ies-in­clud­ed Lisp. It’s about solv­ing prob­lems by mak­ing lan­guages. Lan­guage-ori­ent­ed pro­gram­ming is the name of the game.

The idea has an im­me­di­ate in­tu­itive ap­peal. Per­haps it’s what drove you to Rack­et in the first place. And if it wasn’t, chances are good, if you stick around the com­mu­ni­ty for a while, that you’ll find your­self think­ing about lan­guages.

Look­ing around the Rack­et com­mu­ni­ty & among its fel­low trav­el­ers, one finds that “make your own lan­guage” has a va­ri­ety of sens­es. Al­though some ideas are shared, they get ex­pressed in dif­fer­ent ways. At times, one won­ders: Are we all talk­ing about the same thing?

To help fos­ter the growth of lan­guage-ori­ent­ed pro­gram­ming in gen­er­al—and Rack­et in par­tic­u­lar as the best en­vi­ron­ment for solv­ing prob­lems in that way—it’s im­por­tant to un­der­stand the di­ver­si­ty of mean­ings of “lan­guage-ori­ent­ed pro­gram­ming” and kin­dred ex­pres­sions.

Leave a Comment