gilbert_given_189 wrote:

(after looking at some other languages people have made, I've realized that this kinda resembles another language here…)

gilbert_given_189 wrote:

I had an unfinished proglang that only has the (abstract) interpreter and parser done called Gravy. Its name is a corruption from “curry”, as in currying, which this language uses a lot. That might make it a highly functional language (which, depending on your defintion of “highly functional”, it might be), but it defines some object-oriented paradigm like the object-like “scopes”. (thus, the corruption on the name)

snip

fn foo() {
    return + "foo";
}

print("abc" foo() !); # prints "abcfoo"

davidtheplatform wrote:

gilbert_given_189 wrote:

I had an unfinished proglang that only has the (abstract) interpreter and parser done called Gravy. Its name is a corruption from “curry”, as in currying, which this language uses a lot. That might make it a highly functional language (which, depending on your defintion of “highly functional”, it might be), but it defines some object-oriented paradigm like the object-like “scopes”. (thus, the corruption on the name)

snip

That's probably the most unique language I've seen. Very cool!
Could you return an atom that does an action? Like this:

fn foo() {
    return + "foo";
}

print("abc" foo() !); # prints "abcfoo"

\a.a; # function \a.(# at MEMLOC)
\a.a 1; # number 1
\a.(print (a)); 

Carmiller24 wrote:

I'm (poorly) creating a programming language called Elmwood (Written in Scratch). I need to revamp the syntax, but the goal is to keep it simple.

Redstone1080 wrote:

Sorry for not posting on this. I would normally quote-reply some of these posts but they are way too long lol

Carmiller24 wrote:

I'm (poorly) creating a programming language called Elmwood (Written in Scratch). I need to revamp the syntax, but the goal is to keep it simple.

I tried making one a while ago, called Thatch. The first version of it, called Linear Thatch, can be found here

rdococ wrote:

Redstone1080 wrote:

Sorry for not posting on this. I would normally quote-reply some of these posts but they are way too long lol

Carmiller24 wrote:

I'm (poorly) creating a programming language called Elmwood (Written in Scratch). I need to revamp the syntax, but the goal is to keep it simple.

I tried making one a while ago, called Thatch. The first version of it, called Linear Thatch, can be found here

The easter egg is a nice touch

-

I've got a VM and interface for my language up and running!

The working name for this language is escript. I call it that because “OScript” was taken, and E has the closest object model I could find to it, though the only real similarity is that E and escript both lack classes - instead, objects are essentially records of closures you can create at any time. I'm looking for better name suggestions before release.

Also, any suggestions for better assignment syntax are welcome. Right now it's `<-`, but that blends in with the `->` method/lambda syntax, and while writing the above example I initially typed `:=` by mistake.

gilbert_given_189 wrote:

-snip-
Just asking; what is the instruction set of the VM?
(don't be extensive, just explain some notable ones)

uwv wrote:

not at all a programming language but i've been working on a hdl (hardware descriptor language) specifically targeted at minecraft redstone. im not sure im super happy with the syntax (yet) but i am open to suggestions. i am calling it RDL (Redstone Descriptor Language) and unlike the syntax i am really happy with that

8 bit full adder:

import std/logic/*

assembly full_adder(a, b, cin) -> s, cout { 
  a, b
    -> xor
    -> (take r -> (
         (
           a, b -> and,
           cin, r -> and
         )
         -> or
         -> cout
       )) & ( -> s )
}

assembly eight_bit_adder(a[8], b[8]) {
  var last: full_adder

  repeat sizeof a {
    (
      a[i],
      b[i],
      last[cout] ? 0
    )
    -> ( fulladder -> last -> )[s]
    -> lamp
  }
}

observer clock:

assembly clock() -> p {
  observer > < observer -> p
}

silly little lamp example:

assembly lamp_example() {
  lever -> lamp < observer -> lamp
}

TheSecondGilbert wrote:

(#71)
How would lateral inputs work? (usually called “side inputs”)

uwv wrote:

TheSecondGilbert wrote:

(#71)
How would lateral inputs work? (usually called “side inputs”)

i'm not sure yet, theres no way to do it in syntax, i might just skip giving it syntax and let the synthesizer figure it out

back_input|left_input|right_input -> repeater