<sieni>
Also as opposed to Scheme and Lisp (which are dynamically typed) it is statically typed and as opposed to Haskell and Clean (which are lazily evaluated), Ocaml (and Standard ML) are strictly evaluated like most of programming languages
<AI_coder>
That form handling would naturally lend itself to db access.
<Smerdyakov>
AI_coder, stay tuned; I'm working on a new language that has better form handling than anything I've seen.
<AI_coder>
Is this sarcasm I smell?
<AI_coder>
I think that's what php was.
<Smerdyakov>
No, it's not sarcasm.
<Smerdyakov>
PHP is a joke compared to what I have.
<sieni>
Smerdyakov: which doesn't say much ;-)
<AI_coder>
lol
<AI_coder>
Smerdyakov: Is it compiled, interpreted, what programming languages was it developed in?
<Smerdyakov>
Compiled, and developed in Standard ML.
<AI_coder>
Compiled to what?
<AI_coder>
machine code?
<Smerdyakov>
Yes.
<AI_coder>
I did not intend for that to sound demanding rather I want to know more.
<AI_coder>
Interesting, I presume x86 then.
<Smerdyakov>
No. Anything that MLton targets.
<jer>
Smerdyakov, your wiki page specifically the note about syntax is a little misleading; i come from a smalltalk background and find ML syntax a bit rough to follow (or well, did when i started)
<jer>
and smalltalk's syntax is nothing like c's
<Smerdyakov>
jer, the page is directed at a general audience. The disclaimer might more completely read "other languages with very different syntax."
<jer>
Smerdyakov, i figured as much, my comment was meant to indicate that there are vast languages that aren't ML that don't look at all like C
<Smerdyakov>
I know it, but the situation is that most programmers only know languages that are more or less C syntactically, so that it's necessary give them a little shake and let them know that this isn't all there is.
<dylan>
or algol-like.
<Smerdyakov>
Most programmers today don't have experience with Algol-like languages.
<dylan>
Except all the VB people. But I don't consider them programmers normally. Or humans.
Smerdyakov has quit ["Leaving"]
Skal has joined #ocaml
slipstream-- has joined #ocaml
slipstream has quit [Read error: 110 (Connection timed out)]
ski_ has quit [Read error: 110 (Connection timed out)]
ski_ has joined #ocaml
vodka-goo has joined #ocaml
dark_light has quit ["Fui embora"]
khaladan has joined #ocaml
wimp has joined #ocaml
<wimp>
how can I understand the ocaml optimizing compiler? (I want to write a scheme -> asembly cojmpiler and leverage ocaml's backend)
<sieni>
probably you would have to read the source ^_^
<wimp>
wonderful; nothing better I can hope for?
<joshcryer>
I just tried googling, unfortunately I can't find the paper I was looking for, but it discussed Ocaml's compiler to great depth.
ski_ has quit [Read error: 110 (Connection timed out)]
ski_ has joined #ocaml
m3ga has joined #ocaml
<wimp>
remember any thing about th epaper?
<joshcryer>
Nah, way *way* over my head.
vodka-goo has quit ["Connection reset by by pear"]
<wimp>
no
<wimp>
I jeant
<wimp>
authors
<wimp>
or title
<wimp>
or anythigng>
<joshcryer>
Ooh.
<joshcryer>
No, but, this Ocaml for Scientists thing looks familiar, but it doesn't seem to actually delve into what I read before.