Portable Scheme

Two words that don't belong together.

I would love to use Scheme, but Racket's JIT doesnt expand FFI pointer casts - derefing a C++-pointer is slower than taking a square root. I know pointers are bad, you have to do them on a crappy x86-system, without dynamic typing support. So, in effect, I cant create a minimap for my game, to blit it on screen.

Also, segmentation fault crashes entire DrRacket, while SBCL still allows for easy recovery, without reloading whole application. Scheme is bad for exploratory coding ;_;

>>2
Have you tried Scheme->C implementations, such as Chicken or Gambit?

>>3
Why are you using DrRacket or SBCL at all for games?
You should be using Stalin Scheme.

>>4
>C
If it ain't Lisp, it's crap. And C dont even have eval and JIT.

>>5
Static typing BDSM crap.

LOL

>>6
eval
You're a bad person.

>>9
And C doesn't even have eval and JIT
YHBT dude.

>>10
Not at all. Even assembly language has eval and code as data. Why not C/C++?

>>11
C/C++ do have eval and code as data, they just require you to write your own evaluator.

>>11
Because standard C and SEPPLES^[1] aren't portable assembly languages as that would be an oxymoron.

<sub>____________
1. Don't ever write `C/C++' unless you want to look like a retard.</sub>

>>12
Brainfuck do have eval and code as data, it just requires you to write your own evaluator.

>>13
Don't ever write `C/C++' unless you want to look like a retard.
Writing "C/C++" shows that I dont care. I also write PHP/Python, Perl/Ruby and ML/Haskell, cuz it all the same ugly algol-like shit anyway.

>>13
I've seen this "don't write C/C++" for some time, why should "C/C++" be separately mentioned anyway? In practice SEPPLES' existence is that of a parasite upon the other one.

>>16
People who use C/C++ tend to be C++ programmers who don't know C.

>>17
...or lispers, who hate both languages.

>>18
Lispers are generally neutral towards C.

>>18
CLer here. I wrote more semi-portable C code lately than I wrote Lisp code. Just use the tool that fits the job better. If my needs were better served by C for some task, I have no problem with using it (in the latest case, it involved some pointer arithmetic which is just more trivial to do in C (can be done semi-portably(nearly de facto portable) in CL, but it's still trickier)). I think you have an incorrect view of us which states that we won't touch anything that isn't Lisp: I use what fits my needs. This doesn't mean that when I wrote my C code I didn't see how certain things would have been done much more nicely in Lisp, yet given that that particular C-specific uglyness only occupied some 5 lines of code, it wasn't worth rewriting a small-medium project just for some extra beauty. I don't even participate in the mindless trolling that seems to be going here lately: there's someone hating on Lisp without no valid reason besides his poor taste and then there's someone hating on everything not Lisp for unclear reasons, but surely because the first troll provoked him into counter-spamming.

tl;dr: You have a very flawed image of those that you hate and you don't even understand who they are, what they think and what they do.

>>19
Lispers wrote Unix Haters Hanbook, already when Unix was new and trendy.

>>20
(can be done semi-portably(nearly de facto portable) in CL, but it's still trickier))
A true CLer wouldn't have written unbalanced parentheses.

>>21
I don't think so. Surely they would have been more merciful towards X11.

>>22
A true CLer wouldn't have written unbalanced parentheses.Oh damn... I usuall just use Paredit.
>>21
It's not hard to find things to dislike in a ``worse-is-better'' system when you know a system that ``does-it-right''.

>>23
It's not hard to find things to dislike
This "dislike" contradicts stated "neutrality" of lispers.

javascript is portable scheme

>>24
We're all humans with specific preferences. Where was neutrality claimed? I merely claimed I don't hate anything in particular in any strong manner, that doesn't mean I don't have favorites or that I don't dislike or like particular things. Knowing Lisp biases me in some ways as it teaches you certain elegant patterns and metapatterns that may not always be as elegantly represented in other systems, in which case one can always show their dislike of the way some particular feature was handled. However, this is hardly unique to Lisp, we all tend to become a bit ``elitist'' when we know more optimal solutions to various problems and we see other people choose non-optimal solutions.

>>26
Parentheses are a non-optimal solution to code readability.

C is portable assembly.

>>28
And all that portability makes it slow as fuck!!

>>29
Well they had to include emulation for different architectures in the runtime. You can't have your cake and eat it too.