I have two files a.rkt and b.rkt, a.rkt dynamically requires b.rkt at
syntax time.
a.rkt:
#lang racket
(require (for-syntax compiler/cm-accomplice))
(define-syntax (go stx)
(dynamic-require "b.rkt" #f)
#''success)
(go)
b.rkt:
#lang racket
(when #f
(error 'this-might-break))
If I compile
> I need to pass a file name as a parameter to my program (e.g. test-
> case1.rkt). in that file I just have a list variable.
>
> I want to do it via terminal in this way:
> ---
> racket ./Desktop/a3/1/a3-FC.rkt ./Desktop/a3/1/test-case1.r
Hello,
I need to pass a file name as a parameter to my program (e.g. test-
case1.rkt). in that file I just have a list variable.
I want to do it via terminal in this way:
---
racket ./Desktop/a3/1/a3-FC.rkt ./Desktop/a3/1/test-case1.rkt
-
My personal experience is that a good and detailed design is hard to
get to *without* doing the coding.
-Patrick
On Tue, Mar 19, 2013 at 1:50 PM, Jos Koot wrote:
> One remark down intermixed in your email.
> Jos
>
>> -Original Message-
>> From: users-boun...@racket-lang.org
>> [mailto:u
At Thu, 14 Mar 2013 16:52:20 -0400, "George Rudolph" wrote:
> 2. Where/how can I set the option to use number-style in the bibliography?
> I assumed it was an option in (define-cite), but I cannot figure out how
> to specify it correctly.
Yes, it's an option in `define-cite'.
Here's an exampl
One remark down intermixed in your email.
Jos
> -Original Message-
> From: users-boun...@racket-lang.org
> [mailto:users-boun...@racket-lang.org] On Behalf Of Hendrik Boom
> Sent: martes, 19 de marzo de 2013 15:15
> To: users@racket-lang.org
> Subject: Re: [racket] OFFTOPIC - Quote on Pro
You're right of course. Clearly Brian Kernigan was referring to something
like you describe. Nevertheless I couldn't help arguing that that type of
cleverness is stupid. I started programming late 60ties begin 70ties and
always have had trouble convincing my colleages to think/design/document and
t
This has probably been the aphorism that has guided me most strongly in
coding. I find it even better than the "premature optimization" quip, which
is probably my second favorite, followed by Greenspun's tenth.
Deren
On Mar 18, 2013 9:58 PM, "Harry Spier" wrote:
>
> I found this quote on a blog a
I forget where that quotation came from originally, but it antedated the
days where internal documentation was the norm.
On Tue, Mar 19, 2013 at 06:20:57AM +0100, Jos Koot wrote:
> Well, that may depend on how you define "clever code". Surely it is clever
> to write well documented code that can
I think "clever" here is meant in the "smart-ass" sense.
Let me take this smart-ass definition to be measured by how much you write
"compressed" code (in the sense of Kolmogorov complexity, which
incomputability fits well with the cleverness).
You have a compression function C: Program -> Program
10 matches
Mail list logo
