Re: [racket-users] Custodian problems/ IoT service

The previous code was messy all over the place. This one seems to work, although I'm not sure whether it can keep the services securely sandboxed as intented and won't run out of memory at some point. Revised code: - #lang racket ; tested in Linux (define target-mode #f); #f/

[racket-users] Fwd: Us congress hearing of maan alsaan Money laundry قضية الكونغجرس لغسيل الأموال للمليادير معن الصانع

YouTube videos of U.S. Congress money laundering hearing of Saudi Billionaire " Maan Al sanea" with *bank of America* and The owner of Saad Hospital and Schools in the Eastern Province in *Saudi Arabia* and the Chairman of the Board of Directors of Awal Bank in *Bahrain*

Re: [racket-users] Redex - constraining what is used to fill a hole

On Sunday, December 13, 2015, Sam Caldwell wrote: > > I'm not completely following the design goals here because it seems > > like the desire to reduce only State-Qs could be achieved by writing > > rules that reduced only State-Qs (not arbitrary states). Or are you > > saying

Re: [racket-users] Redex - constraining what is used to fill a hole

> I'm not completely following the design goals here because it seems > like the desire to reduce only State-Qs could be achieved by writing > rules that reduced only State-Qs (not arbitrary states). Or are you > saying that State-Qs are only allowed in the context? If so, then you > could write E

Re: [racket-users] Redex - constraining what is used to fill a hole

I'm not completely following the design goals here because it seems like the desire to reduce only State-Qs could be achieved by writing rules that reduced only State-Qs (not arbitrary states). Or are you saying that State-Qs are only allowed in the context? If so, then you could write E