One recurring complaint is that nobody talks about code on /prog/. So everyone write go and write some code, any code, that does something, anything, and post it. A small explanation wouldn't go amiss either.
String fuckYourShit(String fys)
{
if (fys.equals("Fuck Your Shit"))
return fuckYourShit(fys + " Fuck Your Shit");
else
return fuckYourShit("Fuck Your Shit");
}
Name:
Anonymous2011-03-15 0:09
Fuck Your Shit
Fuck Your Shit Fuck Your Shit
Fuck Your Shit
Fuck Your Shit Fuck Your Shit
Fuck Your Shit
Fuck Your Shit Fuck Your Shit
Fuck Your Shit
Fuck Your Shit Fuck Your Shit
Fuck Your Shit
Fuck Your Shit Fuck Your Shit
Fuck Your Shit
Fuck Your Shit Fuck Your Shit
Fuck Your Shit
Fuck Your Shit Fuck Your Shit
Fuck Your Shit
Fuck Your Shit Fuck Your Shit
Name:
Anonymous2011-03-15 8:01
aStar s h next -> with [0=[s no 0]] []
{:r os:ye? vs
-> o:os.lhd,1 os=:os.ltl // pop lowest scored node
-> next o,0 o,2
|> {ye -> o.{:r [xy p:ye? @_] -> [@p.r xy]} // compile path
;ns -> for [n nG] in ns pG:vs.n // for each viable neighbor
if pG.no? || nG < pG then do // no shorter path?
[[nG+n.h n]=[n o nG] @!os] // g+h
[n=nG @!vs]
-> r os [o,0=o,2 @vs]}}
(constant 'HEADER
[text]<!DOCTYPE NETSCAPE-Bookmark-file-1>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=UTF-8">
<!-- This is an automatically generated file.
It will be read and overwritten.
Do Not Edit! -->
<TITLE>Bookmarks</TITLE>
<H1>Bookmarks</H1>
[/text]
)
>>133 can't handler hundreds of lambdas it produces.Huh, what? SBCL may be slow at compiling things, but it sure as hell can handle them. There are CPS transformers if you really want continuations. As long as you don't constantly generate CPSed code at runtime, you'll be fine.
Name:
Anonymous2011-03-15 15:48
My Postcode: SW1P 1AE
Name:
Anonymous2011-03-15 16:06
>>134
Compile times can be exponential or n^2 to code size. If you use CPS on (list 1, 2, ..., 1000), each entry will produce a continuation, resulting into 1000 lambdas, before `list` gets called.
>>140
I thought it was just a case where one particular compiler didn't perform well as it lacked one type of optimization. I partially chalked up as an extreme/unusual case that doesn't happen much in real programs, but if you think it's a real problem, you're free to file a bug report with SBCL developers - they're available on their bug launchpad, tend to be on IRC most of the time, oh and the source is available so you could try to solve the problem yourself.