Return Styles: Pseud0ch, Terminal, Valhalla, NES, Geocities, Blue Moon. Entire thread

/prog/ programming language design and implementation club

Name: Anonymous 2014-04-29 12:46

Hello this is the first thread of the /prog/ PL design and implementation club!

So what programming languages are you all working on? what stage are you at with it and what ideas are you putting it into it? Have you learned any new things recently that made you change your views?

Name: Anonymous 2014-04-29 12:56

[not language]: flexible sexpr-based library that works as a fully costumisable interprinter on run-time

[language]: ``pure'' functional, declerative programming language with something between C and ML syntax. uses Dependent typing + Uniqueness typing

I am working on the parser but I am lazy

Name: Anonymous 2014-04-29 14:37

I've been wanting to work on a compiler for my own language for a long time now but I haven't even gotten around to writing a spec for the language because I'm a faggot.

Name: Anonymous 2014-04-29 15:29

For a while now I've wanted to build a language for writing game logic in a component-entity paradigm. Part of my goal is to do memory management under the hood wherever possible and make sure the exposed API can be statically checked. I could probably do it as a DSL in Haskell, though.

Name: Anonymous 2014-04-29 16:05

>>2
fully costumisable interprinter on run-time
[sub][sub][sub][b]what[/b][/sub][/sub][/sub]

dependent typing
You know it's not really possible to benefit from dependent types much if your language isn't strongly normalizing aren't and are also able to actually do all kinds of mathematical proofs (otherwise nothing is going to typecheck)?

I haven't even gotten around to writing a spec for the language
Can you give a bit of a description about it? Like what is it etc.
Also SPEC IT YOU FAGGOT

>>4
That sounds really awesome, if you do it as a haskal dsl you can blog about it and get rebbit points

Name: Anonymous 2014-04-30 6:47

what

Name: Anonymous 2014-05-01 11:20

I'm designing a very very toned down version of "C" not compatable really just for my first real compiler.

Name: Anonymous 2014-05-01 12:00

>>7
make it so you can provide leastN-bit integers

Name: Anonymous 2014-05-01 14:03

>>8
I'm going to have the follow integer types: u0 u8 i8 u16 i16 u32 i32 (u0 is void, the rest are signed and unsigned integers) The reason is these all have hardware support on x86. If you want other number types that'd be something to implement as a library or use a higher level language that abstracts away from the hardware. If I get around to 64 bit (which I probabl wont.. it looks hard) I could add 64 bit numbers too.
The fuzzyness of C types always bothered me, sure it's for "portability" but it just makes everything so much more confusing and hard to be sure about.

Newer Posts
Don't change these.
Name: Email:
Entire Thread Thread List