/dpt/ Daily Programming thread

This is /dpt/, the best subreddit of Sup Forums

Umaru-chan edition!

In this thread:
r/programming
r/compsci
r/ReverseEngineering
r/softwaredevelopment

/!\ ** Read this before asking questions ** /!\

mattgemmell.com/what-have-you-tried/
catb.org/~esr/faqs/smart-questions.html


What are you working on?

Other urls found in this thread:

learnlispthehardway.org/
chrisdone.com/posts/haskell-lisp-philosophy-difference
docs.racket-lang.org/
trycode.io/
bootstrapworld.org/
ccs.neu.edu/home/matthias/HtDP2e/
learnxinyminutes.com/docs/racket/
edx.org/course/how-code-simple-data-ubcx-htc1x
edx.org/course/how-code-complex-data-ubcx-htc2x
en.wikipedia.org/wiki/Gay_lisp
twitter.com/SFWRedditVideos

haskell!

i want to cum inside nidalee

>r/programming
>r/compsci
>r/ReverseEngineering
>r/softwaredevelopment
neck yourself
also first for rust is trash

What resources should I use to learn Lisp? This site?

learnlispthehardway.org/

i never use generics

SICP you fool

>neck yourself
good argument, guy
>rust is trash
valid argument, guy

>breaking custom with new shitty format
fu

Reading H&K. I actually really like this book, memes aside. The story layout makes it easy to digest, though, some of it seems pretty outdated to me.

chrisdone.com/posts/haskell-lisp-philosophy-difference

i am using racket.

docs.racket-lang.org/
realm of racket
trycode.io/
bootstrapworld.org/
ccs.neu.edu/home/matthias/HtDP2e/
learnxinyminutes.com/docs/racket/
edx.org/course/how-code-simple-data-ubcx-htc1x
edx.org/course/how-code-complex-data-ubcx-htc2x

i'm using a ball

First for null terminated string are cancerous and need to go.

>comparing to common and emacs lisp
Feels like a straw man desu. Does anyone actually use them anymore?

It's all about scheme and closure. And his statement about monolithic functions in scheme is just wrong.

t. c brainlet

a break isn't needed, just return the value instead when you find it

Whyd you say brainlet, twice?

What a shitty blogpost.

Sage, also neck yourself reddit.

trying to learn python so i can get a better job, but stuck reading books and never writing code and wondering why i still don't know python. also i don't know what to create to improve my skillset. you know, the usual.

>taking the bait

>this are the people on G

Reported for announcing sage

>saying you reported a post
enjoy your ban :^)

so you're saying lisp has adopted the haskell philosophy?

I'm posting on my phone so good luck with that

Thanks for reminding to report OP.

29th for Fortran 90 aka the best Fortran version.

can I get a quick rundown on the changes from Scheme R5RS, Scheme R6RS, and Scheme R7RS

1 or 2 'R's

total programming virgin, been trying to learn javascript for a couple of weeks. what stupid mistake is preventing my capital B counter from working? :(
var Bs = 0
function countBs(word) {
for (var i = 0; i == (word.length - 1); i++){
if (word[i] == 'B'){
Bs++}
}
return Bs;
}


console.log(countBs("BBC"));
//Bs still == 0 no matter what argument I provide

>

replace
i == (word.length - 1)
by
i < word.length

> for (var i = 0; i == (word.length - 1); i++){

for (var i = 0; i < word.length ; i++){

The last two courses - any good?

Also learning racket. Feels good desu

Oh yeah! Loop runs until the condition you provide is no longer true, I must have thought it was the other way round

thanks!

also dont use globals like that. as is you'll get weird results when you call the function twice.
function countBs(word) {
let Bs = 0
for (var i = 0; i

let?

thanks, I think I did have it local to begin with but moved it randomly when I got frustrated not being able to figure out what was wrong haha.
also this but I will google it

If you could only know 3 languages, which would you pick? Let's say you're a rich neet and don't have to choose the most popular to get a code monkey job.

Clisp
C++
java

unironically these 3 cover most things I'd ever really need

C, OCaml, Coq

R6RS is aids.

R7RS is being split up into standard and extras. Standard's pretty close to R5RS. It's getting a specification for library modules, a specification for exceptions that's less labyrinthine than r6rs's, and official requirement for allowing curly and square brackets.

Oh and some dumb fuckers thought it would be a good idea to make it case sensitive.

R7RS large hasn't been fully drafted yet and I'm not exactly sure what makes it distinct from SRFI's, but at least it keeps the C++tards on the steering community from fucking up the R7RS that matters like they did with R6RS.

make my own 2bh

Alright, what are you shit-eating monkeys fucking arguing about now? I see this thread getting bumped every 60 seconds and that only happens when someone is hutt burt.

>Oh and some dumb fuckers thought it would be a good idea to make it case sensitive.
Jesus Christ why
>and official requirement for allowing curly and square brackets.
pretty dank

wrong answers, the correct one was lisp and perl, no third one needed

>perl
why tho?

javascript html and css

Oops I was wrong about { and [. They've been put as "reserved." Eh.

There will be IEEE 754 support, unicode support, case-lambda (pattern matching for procedures), #; to comment out entire s expressions, adding libraries to eval environments, and some other stuff.

VHDL
C#
Not really sure about the third one

sounds cool

/dpt/ still has newer given me a proper use case for Lisp that is only best accomplished by Lisp.

Any app can embed a non bugged lisp interpreter in one day.

maximize the number of necessary parenthesis in a program

racket

assembly, c, and python

my genetic expression language specification is in need of a method of insuring sane mutation to the constants.
my intention is to have the instructions and constants seperate and to just ignore the unused constants, i have deemed the memory overhead acceptable.
so, as an example,
instructions: [8][8][8][8]
constants: [16][16][16][16]
the algorithim i use for mutating/crossing over the instructions is irrelevant, i am more worried about the constants, i don't think mutating them with the instructions will result in "pure" evolution. (imagine a program that only uses 1 constant competing with other programs that use 3, the one that uses 1's mutations might end up taking up the entire "landscape" and push the ones that use 3 out. i think, at least.)
the application that i am targetting will very heavily depend on them, with results ranging from 0% effectiveness to 87%, and the test i intend to run is going to be pretty performance intensive, so i can't easily bruteforce the constants. (and it can't easily be parallelized)
any ideas?
to clarify, the instruction set will include an instruction to acquire a constant, therefore i will require (could probably be optimized out later down the line) the same amount of constants as instructions.

>a proper use case for Lisp that is only best accomplished by Lisp
Any programming task ever.

Name 1 (O N E) specific.

What?

What compiler can I use to compile programs for my graphics card?

As far as I knew they only offered them for DirectX Shading Language, GLSL, and OpenCL.

Adding two integers.

(+ 1 2)

Clean, concise, pure.

> graphics programming
You have to be 18 here, you know.

>going against the foundation of how we read "var op var"
its shit.

Bitch, did you just try and troll me?

What makes you think I'm doing graphics programming? I could be writing compute shaders.

All of math is "function operator", why should an arbitrary set of arithmetic operators be different?

sin 30
abs -4
f(x)

Functional programming, despite having advantages, is also formulaic and too often serves as a vessel for the aggrandizement of vapid establishment pablum.

* that should be, argument

Possibly.

Say it to my face, bitch.

>svo
lmaoing@u
sov or vso are the only reasonable choices. (postfix is better, though)

> functional programming is formulaic
Literally its best feature.

> aggrandizement of vapid establishment pablum
Someone found a thesaurus.

(+ 1 2) is not clean or concise.

Theres ambiguity to how it should be read for people who dont know lisp.

There's ambiguity to how 1 + 2 * 3 should be understood to those who don't know pemdas.

If you don't know something of course you don't know something. You're an idiot.

>Theres ambiguity to how it should be read for people who dont know lisp.
there is ambiguity for 1+2+3 for people who don't know infix notation

you will never make it brainlet

Because you've swallowed the binary operator SVO meme.

Why should some operators be prefix, int(x), and some infix, x+y? It's more concise to have all prefix.

nice strawman.
>It's more concise to have all prefix.
That cant always work

(gas-lisp-autists )

user@user-VirtualBox ~ $ more .bash_profile
#!/bin/bash
PS1='\u:\W|\d:\t \$ '

version() {
arg1=$1
printf "$arg1 : $(apt version $arg1) \n"
}
user@user-VirtualBox ~ $ ./.bash_profile
user@user-VirtualBox ~ $ version vim
version: command not found
user@user-VirtualBox ~ $


what am I doing wrong exactly?
I know like 0 bash, I want to mess around a bit with it, but I'm already getting errors

> That cant always work
Name one.

>That cant always work
it can

Someone's never heard of a reverse polish notation calculator.

There's no good reason to make grade school math notation the norm for all programming languages.

> ./.bash_profile
There should be a space before the slash.

source .bash_profile

thanks m8

Fucking brainlet can't even use maps.

(map gas (filter lisp-autist? thread))

Is this a good book? Working on a small lexer/compiler, but this book has left out some fundamentals I see elsewhere, while project structure etc.

en.wikipedia.org/wiki/Gay_lisp

Anything PEMDAS will have to be separated with a (), right?
So youd have to do shit like this?
(* z(+ x y) )

I pretty much know how to barely read lisp so please correct my syntax.

>assibilation

yes, you are missing a space after zee

idk what pemdas is, because i'm not sthooped

Yeah. Any procedure that you want evaluated gets wrapped in ()'s.

That's what's so neat. There's so few syntax rules.

>wrap everything in ()
>neat

Wrote C and assembly in highschool. Grew up, got jaded and lazy, been writing in Python for years. Decide to try a change and started learning Common Lisp, rewriting a bunch of tools I already made in Python in Lisp to get practice. map functions, tendency to favor recursion. it's a really beautiful clean language, i finally see what I've been missing.

>i have nver written an interpreter in my life

it's
just
easier

As opposed to wrapping certain things in {}, other things in [], then other things in (), then some others have none of these, and some even go within arguments.

Nah.

You can usually use { in most lisps too if you start to miss it after your 30 year long codependent relationship with C++.