I don't have any plans to make the menu-based teachpacks work with #lang languages. They all have require-based interfaces, tho (eg (require 2htdp/image) and (require htdp/image)); are those not sufficient somehow?
Robby On Tue, Jul 12, 2011 at 12:35 PM, Danny Yoo <[email protected]> wrote: > So let's say that I'm designing a new #lang-implemented language. I'd > love to automatically work with teachpacks and other external modules. > So I can get require-like functionality with my language, and that > seems to work ok. > > But when I click on Language/Add Teachpack, DrRacket responds by > saying that teachpacks only work with the teaching languages. > > What's required for a #lang-implemented language to be treated as a > teaching language, and what does it need to implement to get teachpack > support? Thanks! > _________________________________________________ > For list-related administrative tasks: > http://lists.racket-lang.org/listinfo/users > _________________________________________________ For list-related administrative tasks: http://lists.racket-lang.org/listinfo/users
