/prog/'s own esoteric language

Fun idea. Let's make our own programming language.
Conditions:
Must be somewhat useful like ABC.
Not limited to characters only. Can include words.
1 function per post.

Sounds somewhat like the Adjudicated Blind Collaborative Design Esolang Factory, except not quite Blind.

http://www.esolangs.org/wiki/Adjudicated_Blind_Collaborative_Design_Esolang_Factory

The most recent result was http://www.harderweb.de/tmp_jix/allofthem.txt

LISP: jump to the beginning of the stack.

Must be somewhat useful like ABC.

ifeelkindabadaboutit:( - Terminate program

All functions must be written in parens () ala lisp.

>>6
Just make it send messages to objects:
poster6 (extract-anus) (hax)

Poster6 receives 'extract-anus' and returns its anus, which then receives 'hax' and promptly haxes itself.

All lines of code must start with >> and a number.  Then you can goto considered harmful to a line of code.

The official name of the language is [spoiler]/prog/[/spoiler]

http://en.wikipedia.org/wiki/LOLCODE

>>11 process (extract-thread 0) (goto-considered-harmful >>15)

Update:
LISP: Jump to the beginning of the stack
ifeelkindabadaboutit:(: Terminate program
>>X: Marks a line
goto considered harmful: Jump to a line marked with >>X

Keep it going. :)

I suggest adding a recursive factorial to the standard library.

http://esolangs.org/wiki/IRP

Leah Culver: generating a random number between 0-100 and putting it on the stack

>>7
An anus cannot hax itself.

>>16
Have you checked?

A language is just a language, but a Fig Newton is fruit and cake.

>>11
I love it.  Lets keep going.

pee: increments top of stack

needs moar car and cdr.

(my-other [var name] is-a [var name])

Swap two variables

Update:
LISP: Jump to the beginning of the stack
ifeelkindabadaboutit:(: Terminate program
>>X: Marks a line
goto considered harmful: Jump to a line marked with >>X
Leah Culver: generating a random number between 0-100 and putting it on the stack
pee: increments top of stack
(my-other [var name] is-a [var name]): Swap two variables

Keep it going. :)

(post "Text here" numberhere)

Make a post on prog.  Example:
(post "shut up >>24" 1217887165)

abc "program"

Run an ABC program.
http://esolangs.org/wiki/ABC

The Sussman: deletes stack

The Sussman: deletes stack

rape: pop stack
penis: push stack

>>25
By analogy:

run "filename"

Ignores the rest of the code and just executes the named program, which can be written in an actual programming language.

(car list) return first element of the list.
(cdr list) return second to last elements of the list.

>>29
TOURING COMPLETENESS ACHIEVED!

Update:
LISP: Jump to the beginning of the stack
ifeelkindabadaboutit:(: Terminate program
>>X: Marks a line
goto considered harmful: Jump to a line marked with >>X
Leah Culver: generating a random number between 0-100 and putting it on the stack
pee: increments top of stack
(my-other [var name] is-a [var name]): Swap two variables
The Sussman: deletes stack
rape: pop stack
penis: push stack


Keep it going. :)

shit: decrement top of stack

>>30
I suggest:
car: move down the stack by one
cdr: move up the stack

CFLAGS JUST KICKED IN YO: optimize all the program into a single NOP.

>>35,29
Keep it real.

>>35
CFLAGS JUST KICKED IN YO: Skip next command.

nowYouHaveTwoProblems -- double the top element of the stack.

>>38 should be fork

>>39
I support your idea.

/b/ -- Overwrites every pointer with DICK

spork()

Fork the code into a separate thread.

(factor x) instantly returns the prime factors of x.

DONTHELPHIM: generate an exception

*grabs debugger* - breakpoint instruction

Update:
LISP: Jump to the beginning of the stack
ifeelkindabadaboutit:(: Terminate program
>>X: Marks a line
goto considered harmful: Jump to mark >>X
Leah Culver: generating a random number between 0-100 and putting it on the stack
pee: increments top of stack
shit: decrement top of stack
(my-other [number] is-a [number]): Swap two positions of the stack
The Sussman: deletes stack
rape: pop stack
penis: push stack
(factor x): instantly returns the prime factors of x.
CFLAGS JUST KICKED IN YO: Replace next command with a random command.
DONTHELPHIM: Skip next command.


Keep it going. :)

>>45
*grabs ASCII* Prints top of stack as an ASCII character.

Every single program written will not work.

>>48
huh

>>48
/thread

Appendix A.  Complete [spoiler]/prog/[/spoiler] implementation, written in The Algorithmic Language Haskell for rapid development.

main = fail "wut"


 _____ _    ____ _  _____ _   _ _   ____ ___ ____   ____  _____ _   _ ___ ____  _
|  ___/ \  / ___| |/ /_ _| \ | ( ) | __ )_ _/ ___| |  _ \| ____| \ | |_ _/ ___|| |
| |_ / _ \| |   | ' / | ||  \| |/  |  _ \| | |  _  | |_) |  _| |  \| || |\___ \| |
|  _/ ___ \ |___| . \ | || |\  |   | |_) | | |_| | |  __/| |___| |\  || | ___) |_|
|_|/_/   \_\____|_|\_\___|_| \_|   |____/___\____| |_|   |_____|_| \_|___|____/(_)

>>52
Hello, Patrik.

>>53
Hello, Bob.

Name of the language will be /prog/oteric

>>55
Sounds pretty good.

>>52
Sounds pretty good.

    __                        __
   / / __  _ __ ___   __ _   / /
  / / '_ \| '__/ _ \ / _` | / /
 / /| |_) | | | (_) | (_| |/ / 
/_/ | .__/|_|  \___/ \__, /_/  
    |_|              |___/

private variables are declared inside [spoiler] tags

NULL expansion:
If the preprocessor sees NULLx# where # is a non-negative integer it will be replaced with NULL # times.

Example:
foo(NULLx6);
expands to
foo(NULL, NULL, NULL, NULL, NULL, NULL);

NULLx0 is undefined.

>>60
Surely foo(NULLx0) should just be foo().

>>60
As a an EXPERT WINDOWS PROGRAMMER I approve of this design decision.


FORCED stdio OF dick;
[testclass]
  [spoiler]
    hello <- [quote]Hello, world![/quote]
  [/spoiler]
  [def /testclass NULLx2]
    *grabs dick*
    /puts self.hello
  [/def]
[/testclass]

testclass NULLx2
/b/
ifeelkindofbadaboutit

Keep it going. :)

Fuck you.

>>67

Multiplication

Keep it going. :)

I think we should adapt some better coding standards. All commands should be in a standardized format, eg:
*grabs X* for stack manipulation as in
stack.*grabs The Sussman* empties a stack, etc.

Flow operations could be in the format "flow:" and ignore whitespace and case, eg:
flow:i  f e e l  k i n d  o f  b a d  a b o u t  i t  : (

"If" statements could use the OMGCOMMANDS, which are capitalized orders:
if( anus.haxed == true )
   DONTHELPHIM;
anus.hax;


Anyway, just some ideas, but if we want a working interpreter soon we better not have 50 keywords, all with different usage and syntax.

>>70
Good ideas. Can you improve the list, please?

bump

This is going to be another LOLCODE, right?

>>73
even uglier then lolcode by the looks of it

>>74
then

(comefrom <line>)
After evaluating line <line>, continue execution here.

>>76
example program:
(comefrom 2)
(display "LISP")

comefrom considered beneficial

(comehere <line>)
Moves <line> right after the instruction pointer.

hai guys am i doin it rite? hai guys am i doin it rite? hai guys am i doin it rite? hai guys am i doin it rite? hai guys am i doin it rite? hai guys am i doin it rite? hai guys am i doin it rite? hai guys am i doin it rite? hai guys am i doin it rite? hai guys am i doin it rite? hai guys am i doin it rite? hai guys am i doin it rite? hai guys am i doin it rite? hai guys am i doin it rite? hai guys am i doin it rite? hai guys am i doin it rite? hai guys am i doin it rite? hai guys am i doin it rite? hai guys am i doin it rite? hai guys am i doin it rite? hai guys am i doin it rite? hai guys am i doin it rite? hai guys am i doin it rite? hai guys am i doin it rite? hai guys am i doin it rite? hai guys am i doin it rite? hai guys am i doin it rite? hai guys am i doin it rite? hai guys am i doin it rite? hai guys am i doin it rite? hai guys am i doin it rite? hai guys am i doin it rite? hai guys am i doin it rite? hai guys am i doin it rite? hai guys am i doin it rite? hai guys am i doin it rite? hai guys am i doin it rite? hai guys am i doin it rite? hai guys am i doin it rite? hai guys am i doin it rite? hai guys am i doin it rite? hai guys am i doin it rite? hai guys am i doin it rite? hai guys am i doin it rite? hai guys am i doin it rite? hai guys am i doin it rite? hai guys am i doin it rite? hai guys am i doin it rite? hai guys am i doin it rite? hai guys am i doin it rite? hai guys am i doin it rite? hai guys am i doin it rite? hai guys am i doin it rite? hai guys am i doin it rite? hai guys am i doin it rite? hai guys am i doin it rite? hai guys am i doin it rite? hai guys am i doin it rite? hai guys am i doin it rite? hai guys am i doin it rite? hai guys am i doin it rite? hai guys am i doin it rite? hai guys am i doin it rite? hai guys am i doin it rite? hai guys am i doin it rite? hai guys am i doin it rite? hai guys am i doin it rite? hai guys am i doin it rite? hai guys am i doin it rite? hai guys am i doin it rite? hai guys am i doin it rite? hai guys am i doin it rite? hai guys am i doin it rite? hai guys am i doin it rite? hai guys am i doin it rite? hai guys am i doin it rite? hai guys am i doin it rite? hai guys am i doin it rite? hai guys am i doin it rite? hai guys am i doin it rite? hai guys am i doin it rite? hai guys am i doin it rite? hai guys am i doin it rite? hai guys am i doin it rite? hai guys am i doin it rite? hai guys am i doin it rite? hai guys am i doin it rite? hai guys am i doin it rite? hai guys am i doin it rite? hai guys am i doin it rite? hai guys am i doin it rite? hai guys am i doin it rite? hai guys am i doin it rite? hai guys am i doin it rite? hai guys am i doin it rite? hai guys am i doin it rite? hai guys am i doin it rite? hai guys am i doin it rite? hai guys am i doin it rite? hai guys am i doin it rite? hai guys am i doin it rite? hai guys am i doin it rite? hai guys am i doin it rite? hai guys am i doin it rite? hai guys am i doin it rite? hai guys am i doin it rite? hai guys am i doin it rite? hai guys am i doin it rite? hai guys am i doin it rite? hai guys am i doin it rite? hai guys am i doin it rite? hai guys am i doin it rite? hai guys am i doin it rite? hai guys am i doin it rite? hai guys am i doin it rite? hai guys am i doin it rite? hai guys am i doin it rite? hai guys am i doin it rite? hai guys am i doin it rite? hai guys am i doin it rite? hai guys am i doin it rite? hai guys am i doin it rite? hai guys am i doin it rite? hai guys am i doin it rite? hai guys am i doin it rite? hai guys am i doin it rite? hai guys am i doin it rite? hai guys am i doin it rite? hai guys am i doin it rite? hai guys am i doin it rite? hai guys am i doin it rite? hai guys am i doin it rite? hai guys am i doin it rite? hai guys am i doin it rite? hai guys am i doin it rite? hai guys am i doin it rite? hai guys am i doin it rite? hai guys am i doin it rite?

wtf crack dat shit nigger

bump. keep em coming. :)


(goaway <line>)         ; gets rid of <line>
(pleasecomeback <line>) ; May get the previously gotten rid of line back at position <line>, maybe not.
(iloveyou <line>)       ; Copies <line> if called once, removes the whole subroutine if called twice.

some std library functions:

(copypasta sha1_hash) - returns sjis art/copypasta/etc.  the implementation should recurse through a folder of copypasta provided with the distro as well as a user's .copypasta/ directory.

(ircd port) - starts an ircd listening on the given port

(thread id) - fetches thread id from /prog/.  the returned thread object formats itself when printed and has methods to print individual posts.

IN B4event
    event trapping/handling
    including errors, intervals &stuff
KTHX

EXPERT PROGRAMMER
    assembly program
KTHX

I EETEDvar # or proc
nulls var/proc - integers/floats/whatsit set to 0, strings set to "", procs set to "end".

DO NOT WANTvar # or proc
clears var completely, including pointers. I EETED does this to booleans.

PROCproc CONSIDERED HARMFUL
stops any execution of proc, and future attempts at execution produce errors

VARvar CONSIDERED HARMFUL
for vehemently disusing variables

And, of course, attempts to use elements that are CONSIDERED HARMFUL, would be one of the events trapped by IN B4.

And of course, the space before /code just has to be removed, making the code look even uglier than intended!

>>85
Fuck off.

(import math)

(class Example (object)
  (def (__init__ x y)
    (multiple-def (self.x self.y) (x y)))
  (def angle (property (lambda (self) (math.atan (/ self.y self.x)))))
  (def radius (property (lambda (self) (** (+ (* self.x self.x) (* self.y self.y)) .5) )))
  (def (repr self)
    (% '(Example %s %s)' (repr self.x) (repr self.y)))
)

(print (map (lambda (x) (x.upper)) 'This is the language of my dreams; the forcibly Lisped language Lython... Lisp syntax, Python semantics, object system and library.'))

>>88
Ew, extra paren after x.upper, sorry. No parens matching in browser.

Another example:

(for x (xrange 1 11)
  (for y (xrange 1 11)
    (print (% '%4d' (* x y)))))

As you can see, filthy statements are turned into beautiful expressions.

>>89
Wait. let's reserve ', ` and company for quote, quasiquote and company macros. Strings could be represented with " and nestable Tcl or Perl-like quotes with braces. Dictionaries and sets specified as (dict (k1 v1) ...) and (objectset e ...). . and [] should be advanced macro shorthands for get/set!, which in turn are macros for the actual double-underscore methods that get called behind the scenes. Variables are defined with (def var value) and rebound with (= var value) (a slight change from Python's semantics for better closures); use (== item ...) to compare. All filthy statements are now expressions and return the last evaluated value (e.g. the value of the last expression in the last iteration of a while loop). Lambdas are, thus, as powerful as defs. Tail-call elimination is guaranteed to happen.

This would probably be Guido's worst nightmare. And this is exactly what he'd need to do to the language; perhaps minus the Lisp syntax.

>>90
print is already a function in python 3.0, you can already do assignment without a var=value statement by setattr() and locals() (or even globals()), for and while loops aren't functional anyway, and the rest is just differences of syntax.

>>91
Python does need a better syntax to create multi-line closures. I think I remember hearing about a PEP to have a Ruby-like syntax for it (albeit with FIOC) though I don't know how well it went over.

>>90
Guido hates folds.
"So now reduce(). This is actually the one I've always hated most, because, apart from a few examples involving + or *, almost every time I see a reduce() call with a non-trivial function argument, I need to grab pen and paper to diagram what's actually being fed into that function before I understand what the reduce() is supposed to do. So in my mind, the applicability of reduce() is pretty much limited to associative operators, and in all other cases it's better to write out the accumulation loop explicitly.

>>93
How does he write functional code?

>>94
By indenting it until he's convinced it's now functional.

He hates reduce because he can't understand its use, so you should always write loops explicitly.

>>94
Terrible!

>>93
Hurrr I hate what I don't understand.

Sounds like Linux Tornballs.

>>98
Except Guido hasn't produced anything of value.

>>99
http://www.isc.org/sources/devel/func/glob.php

unfortunately he hasn't produced anything nearly as good since then.

>>100
100GET.
100 is the HTTP response code to Continue.
So by all means, please Continue.