Programming Languages

1186 readers

1 users here now

Hello!

This is the current Lemmy equivalent of https://www.reddit.com/r/ProgrammingLanguages/.

The content and rules are the same here as they are over there. Taken directly from the /r/ProgrammingLanguages overview:

This community is dedicated to the theory, design and implementation of programming languages.

Be nice to each other. Flame wars and rants are not welcomed. Please also put some effort into your post.

This isn't the right place to ask questions such as "What language should I use for X", "what language should I learn", and "what's your favorite language". Such questions should be posted in /c/learn_programming or /c/programming.

This is the right place for posts like the following:

"Check out this new language I've been working on!"
"Here's a blog post on how I implemented static type checking into this compiler"
"I want to write a compiler, where do I start?"
"How does the Java compiler work? How does it handle forward declarations/imports/targeting multiple platforms/?"
"How should I test my compiler? How are other compilers and interpreters like gcc, Java, and python tested?"
"What are the pros/cons of ?"
"Compare and contrast vs. "
"Confused about the semantics of this language"
"Proceedings from PLDI / OOPSLA / ICFP / "

See /r/ProgrammingLanguages for specific examples

Related online communities

founded 1 year ago

MODERATORS

armchair_progamer

July 2023 monthly "What are you working on?" thread (self.programming_languages)

submitted 1 year ago by armchair_progamer to c/programming_languages

14 comments fedilink hide all child comments

How much progress have you made since last time? What new ideas have you stumbled upon, what old ideas have you abandoned? What new projects have you started? What are you working on?

Once again, feel free to share anything you’ve been working on, old or new, simple or complex, tiny or huge, whether you want to share and discuss it, or simply brag about it - or just about anything you feel like sharing!

The monthly thread is the place for you to engage /c/programming_languages on things that you might not have wanted to put up a post for - progress, ideas, maybe even a slick new chair you built in your garage. Share your projects and thoughts on others’ ideas, and most importantly, have a great and productive month!

Also see: https://www.reddit.com/r/ProgrammingLanguages/comments/14ngaly/july_2023_monthly_what_are_you_working_on_thread/

you are viewing a single comment's thread
view the rest of the comments

[–] K2yfi 5 points 1 year ago* (last edited 1 year ago)

I'm making an engineering language where just about everything is an expression. Lately the most interesting thing to me is the juxtapose operator, i.e. if you stick two expressions next to each other without whitespace, they are considered juxtaposed. Initially juxtapose was just going to be for math/multiplication, but I've also decided to make function calling handled via juxtapose as well (since it lets me get rid of several types of syntax and replace them with pure expression handling)

Some interesting examples:

since the quotes delimit the string, you don't need the parenthesis
```
printl'Hello, World!'
```
though sometimes you need to disambiguate with parenthesis
```
s = "Hello, World!"
printl(s)
```
technically you can wrap either operand, so long as they touch
```
(printl)s  // though this is bad style for function calls
```

this has a neat consequence that string prefixes are just functions, and work pretty seamlessly

mypath = p"this/is/some/path/object"
myregex = re"[^i*&2@]"
myphonetics = ipa"ɛt vɔkavit dɛus aɾidam tɛɾam kɔngɾɛgatsiɔnɛskwɛ"

p, re, and ipa are all just ordinary functions

some basic math examples
```
x = 3
y = 2x
z = (2+3y)(x*2)
```
complex numbers/quaternions are pretty seamless
```
1 + 2i
1 + 2i + 3j + 4k
```

also physical units will be first class citizens, and fit in pretty nicely with juxtapose

15kg
7(kg) * 10(m/s/s)
25(N/m^2) + 15(Pa)
1500(W) / 10(A)
5(A) * 2(Ω)
8(m*s^-1) / 2(s)
40(N*m) * 10(rad)
1000(m^3) * 2(kg/m^3)

Where it gets really wacky/hard to parse is something like this
```
sin(x)^2 + cos(x)^2    // => (sin(x))^2 + (cos(x))^2
```
depending on the types of sin and cos different things can happen. By default sin/cos are functions, so the function call happens first, but if the user redefined them or constructed an identically formatted expression where they are numeric, then the exponent should happen first
```
s = 10
c = 20
s(x)^2 + c(x)^2    // => s(x^2) + c(x^2)
```
but that's all just a problem for the compiler

Been working on and off on an interpreter/compiler written in python. Pretty slow going though.