Re: [racket] Rackunit best practices

Thanks everyone for their feedback. Keep it coming! I didn't know about the ability to include tests next to the source code a la literate-programming. A fantastic feature. I'll try it out personally. I am, though, concerned that my tests will obscure the code that executes it. >From the many

Re: [racket] Rackunit best practices

On Fri, Aug 23, 2013 at 12:14 AM, Greg Hendershott < greghendersh...@gmail.com> wrote: > In my opinion the "most Rackety" way to do tests these days is what > Laurent mentioned: The `test` submodule. > When the tests become too long, I prefer to put them in a separate file though. > (Although w

[racket] Signature for an optional-argument function?

Right now I'm using Intermediate Student Language, not Racket, because I don't know Racket and I've been taking Introduction to Systematic Program Design - Part I online, which is based on HtDP, or How to Design Programs. I was wondering if I could define a function with optional arguments,

[racket] OpenCL module macro errors

Hi all, I'm a little new to Racket (and Lispy languages in general). I'm working on extending the OpenCL module to add support for OpenGL context sharing. My questions are somewhat specific to the OpenCL module, but hopefully I can provide enough context to minimize that. Right now I'm work

Re: [racket] current-module-declare-name

You're unlikely to see a non-`#f` value for that parameter. The parameter is set by the module loader while a module file is being loaded, which includes when the module is declared but declaration and instantiation are distinct. The time that code runs within a module is instantiation time, w

Re: [racket] Rackunit best practices

In my opinion the "most Rackety" way to do tests these days is what Laurent mentioned: The `test` submodule. 1. It's easy to run the tests in foo.rkt file: `raco test -x foo.rkt`. 2. It's easy to write the tests -- no extra source file required. 3. You can even write tests adjacent to the defini

[racket] current-module-declare-name

(current-module-declare-name) seems to always return #f. It does this both when I run it from the REPL, when it run it from an unsaved file, and when I run it from a saved file. Is this function performing properly? Under what circumstances should it return #f? Just so you know, I have canvas

Re: [racket] realm of racket problems

Glad to hear DrRacket helped you. Don't hesitate to ask for help, but let me recommend the Racket user list: users@racket-lang.org You can sign up at the Racket lang.org web site and the list members are helpful and quick to jump in. -- Matthias On Aug 22, 2013, at 1:51 PM, Neal Aggarw

[racket] ICFP 2013 Call for Participation

[ Today is the last day of early registration. ] == == CALL FOR PARTICIPATION 18th ACM SIGPLAN International Conference on Functional Programming ICFP 2013 Boston, MA, USA, 25-27 September 2013 Affiliated events 22-24 September

Re: [racket] Rackunit best practices

Thanks for the idea but I think it's worth explaining the bigger picture a bit in addition to the detail answers you have received. ;; Part of Racket's slogan is 'internalize tools from the tool chain into the language' Tests have re