Re: [racket] Style guide question (limited syntax transformation language)

2012-10-06 Thread Matthias Felleisen
No. Our macros are procedural, meaning you often write functions that manipulate syntax. We now have define-for-syntax for this purpose and people should use it, not write one huge 'lambda' inside of define-syntax (parse, case, rules). On Oct 6, 2012, at 11:28 AM, Lorenz Köhl wrote: > Th

[racket] Style guide question (limited syntax transformation language)

2012-10-06 Thread Lorenz Köhl
There's this paragraph in the style guide I don't understand: > For many years we had a limited syntax transformation language that forced > people to create huge functions. This is no longer the case, so we should try > to stick to the rule whenever possible. >From http://www.ccs.neu.edu/home/m

Re: [racket] HTTP-POST byte string gets truncated

2012-10-06 Thread Gregory Woodhouse
I'm not sure what's going on, but the HTTP protocol specifies that the header and message body be separated by \r\n\r\n. Sent from my iPhone On Oct 6, 2012, at 3:50 AM, Mikko Tiihonen wrote: > Hi, again! > > I'm continuing to build a small HTTP-client. The problem is now that the POST > par

[racket] HTTP-POST byte string gets truncated

2012-10-06 Thread Mikko Tiihonen
Hi, again! I'm continuing to build a small HTTP-client. The problem is now that the POST parameter/value byte strings sent by put-pure-port and post-pure-port seem to get truncated somewhere. The request-post-data/raw shows that the byte string gets prepended with "\r\n\r\n" and truncated by fo