Using the `--enable-libs` flag to `configure` should get you
"libracket3m.a" in the installation's "lib" directory after installing.
If you're using the top-level makefile from the git repository (as
opposed to, say, a snapshot source bundle from
http://plt.eecs.northwestern.edu/snapshots/ or
http:
10 hours ago, Jay McCarthy wrote:
> I didn't respond to this thread originally because I believe that
> Racket is generally "anti-stubbing". [...]
10 hours ago, Greg Hendershott wrote:
>
> I think it's kind of a "language smell" when people need to use
> tools to create projects. I like that Rack
I am using Racket as a scripting language for Vim. I believe that the
number of people who use Racket instead of VimL is not very small. I live
in a town with 60 inhabitants, and at least 40 persons use Racket to
script Vim. Therefore, I wonder whether the new release of Racket will be
compati
On Dec 14, 2013, at 7:09 AM, Greg Hendershott wrote:
I'd also be perfectly happy with `raco new ` w/ a boilerplate
project w/ a module, tests, and doco stubbed out.
>>> `raco pkg new` (or `raco pkg init`).
>>> A `raco pkg git-new` and a `raco pkg github-new` that do all the boring
>>> s
My son, who I'm afraid/inspired to say is a DrRacket addict, in that he does
much of his homework (physics, calculus, Latin, music, what-next...) in
DrRacket, has read through the Racket GUI Toolkit docs at:
http://docs.racket-lang.org/gui/
and presto, he has an app that can conjugate or declin
On second thought, you are right, and all your points are valid. The
incremental part is the most important aspect of package development.
And if by "anti-stubbing" you mean "if you need a stub, then something in
the design is wrong", then this is a very nice principle, although probably
quite diff
Greg Hendershott wrote at 12/14/2013 10:09 AM:
- info.rkt with a few incantations
"info.rkt" is the one thing for which ``stubs'' appear appropriate.
This is why McFly generates/updates "info.rkt". (At bottom of this
message is an example stubbed "info.rkt" that I made by going into my
>>> I'd also be perfectly happy with `raco new ` w/ a boilerplate
>>> project w/ a module, tests, and doco stubbed out.
>> `raco pkg new` (or `raco pkg init`).
>> A `raco pkg git-new` and a `raco pkg github-new` that do all the boring
>> stuff for you may also be quite convenient, if such things ar
I didn't respond to this thread originally because I believe that
Racket is generally "anti-stubbing". The concept of a "racket project"
basically doesn't exist, because everything is supposed to be "inside"
the language. For instance, if you want to create a module with tests,
then you just create
On Fri, Dec 13, 2013 at 11:14 PM, Ryan Davis wrote:
> I'd also be perfectly happy with `raco new ` w/ a boilerplate
> project w/ a module, tests, and doco stubbed out.
>
> Is there anything in the package ecosystem like this?
>
Not that I know of, but it's a good idea. It would probably look mor
10 matches
Mail list logo
