[racket] What are the roles for teachpacks these days?

From: Todd O'Bryan (toddobryan at gmail.com)
Date: Tue Jul 12 16:05:26 EDT 2011

Yeah. Could we just have the Language menu and Teachpacks fade away?

I've been bitten so many times by the hidden stuff that I think it's
easier to have students explicitly write

#lang htdp/bsl
(require 2htdp/image)

at the top of files. I'd prefer something like #lang beginner, but I
don't really care so long as it's explicit and not too complicated.


On Tue, Jul 12, 2011 at 3:54 PM, Robby Findler
<robby at eecs.northwestern.edu> wrote:
> 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 <dyoo at cs.wpi.edu> 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

Posted on the users mailing list.