>If binary, ASM, and C were the only programming languages and anyone who invented another programming language were executed by the state.
 CRIME Shirt $21.68 |
 Nothing Ever Happens Shirt $21.68 |
CRIME Shirt $21.68 |
>If binary, ASM, and C were the only programming languages and anyone who invented another programming language were executed by the state.
>having to walk your robo dog
Thank god it didn't happen.
the dog is walking him, anon
You mean
>if everything ran on Lisp
C wouldn't exist because the people who made C didn't invent anything and just copied from other languages.
that hardly matters when it's the G.O.A.T. It just werks
>It just werks
The only thing that "just werks" in C is buffer overflow exploits.
yourself in the foot
>why was i allowed to do that?
skill issue
Practically nobody is skilled then judging by CVE numbers
everbody isnt me, scrub.
theres just too many welders in the programming field.
Post your projects
thats a cheap shot. you know that i wont.
ill post one of my makefiles instead
this i can disclose
NAME := sdl-test
CC := gcc
DDIR := build/
ODIR := obj/
IDIR := inc/
SDIR := src/
BUILD_DIRS := $(DDIR) $(ODIR) $(IDIR) $(SDIR)
LIBS_ROOT := /home/aaa/code/libs/
LIBS := lib_sys
LIBS_PATHS := $(foreach LIB, $(LIBS), $(LIBS_ROOT)$(LIB)/build/$(LIB).a)
LIBS_DEPS := $(foreach LIB, $(LIBS),
$(shell find $(LIBS_ROOT)$(LIB)/ -name *.h | sed 's/^.///g'))
LIBS_FOLDERS := $(foreach LIB, $(LIBS), $(LIBS_ROOT)$(LIB)/build/)
LIBS_FLAG := $(foreach lib_folder, $(LIBS_FOLDERS), -I $(lib_folder))
SRCS := $(shell find $(SDIR) -name *.c | sed 's/^.///g')
OBJS := $(addsuffix .o, $(basename $(SRCS*~~
DEPS := $(shell find $(IDIR) -name *.h| sed 's/^.///g')
VPATH := %.o obj
FLAGS := -I $(IDIR) $(LIBS_FLAG) -O3 -lSDL2
%.o: %.c $(DEPS)
@mkdir -p $(ODIR)$(dir $@)
$(CC) -c -o $(ODIR)$@ $< $(FLAGS) $(LIBS_FLAG)
all : clear_console _all
_all : message_build $(OBJS)
$(CC) -o $(DDIR)$(NAME) $(addprefix $(ODIR), $(OBJS)) $(FLAGS) $(LIBS_PATHS)
clean : clear_console _clean
_clean :
@echo ---clearing objects
rm -f $(shell find $(ODIR) -name *.o)
re : clear_console _clean _all
message_build :
@echo ---building
@mkdir -p $(DDIR)
clear_console: clear_destination
@clear
clear_destination:
@echo ---clearing destination
rm -f $(DDIR)*
init: clear_console
@echo ---initializing
mkdir -p $(BUILD_DIRS)
test:
echo $(LIBS_PATHS)
echo $(LIBS_DEPS)
echo $(LIBS_FOLDERS)
echo $(LIBS_FLAG)
unless you wanna have a look at the first 200 lines of my current sdl/opengl learning project...
>sdl/opengl
nice. I'm doing a software rendering project now. I want to make it portable and see what kind of hardware I can get it running on. good luck.
thanks,
>what kind of hardware i can get it running on
that sounds very interesting. and difficult if one factors in fridges, calculators, and such.
but also very rewarding.
good luck to you too. post your advancements, im eager to hear more about that
(just spotted a mistake btw. i define the path to the includes of my libs twice when i create the .o objects)
>a mistake
No, you obviously meant to do that
After all, you're a real C programmer
You don't make mistakes
a *mistake, not an *error
its not the same.
and
>real C programmer
i had this discussion already.
and im *becoming one. i am not yet a fully fledged C programmer.
i can do anything i want.
but i have yet to learn the best ways to do it
Nobody at Bell Labs has ever been a real C programmer. Their code is full of errors and mistakes.
that sucks.
not leaving anything behind is just a matter of being systematical in C.
yes, sometimes it implies going through thousands of lines of the source the libs are built upon
but you gain some you lose some
code ownership. its one of the reasons i almost exclusively use my own libraries
(cont.)
i got a better solution:
how bout you just become a welder?
i know welding too. its fun. its challenging. you gotta use your brains. theres stuff to know. procedures, chemistry, physics.
its an interesting subject. you should try, since C is giving you such a hard time
>this suggestion kills the dumbass C strugglers
there isnt such thing as a C struggler.
just like in construction-
theres apprentices
theres journeymen
theres masters
and then theres the people who cant cut a dryboard
>and then theres the people who cant cut a dryboard
these people actually overlap with people who just cant into C.
you need a certain practical sense when dealing with the language. and with dryboards.
>its an interesting subject. you should try, since C is giving you such a hard time
You should tell that to Dennis Ritchie and Ken Thompson.
im pretty sure they either did or would appreciate welding too.
>binary
>programming language
high schoolers pls go
>programming languages are non-binary
>just like me
Pretty sure he means machine code aka binaries
Why do only high school dropout incels say things like these?
it's funny how much incels screech about communism, but then will espouse shit like this. reminder that horseshoe theory is heckin real and valid
>all autoritarianism is communism
ugh. liberliasm is a mental disease
C programmers believe that C is Computational Marxism. They're extreme communists.
C is free speech, transparency, security, efficiency, effectiveness, unregulated freedom and pure, unadulterated, uncucked, gold-patterned laisez faire capitalism. Truly the language of freedom chads.
News flash, authoritarianism is good if the people in power are making society better. And bad if the people in power are making society worse. They would be making it better by limiting programming languages.
this
you're a crack-head
>They would be making it better by limiting programming languages.
The only programming language that would make society better by not existing is C.
>News flash, authoritarianism is good if the people in power are making society better.
yes we know incel. as long as you are in power everything will be just dandy
id rather have him as leader than a bunch of C-suites who want me dead bc they got their lunchmoney taken when kids
>and anyone who invented another programming language were executed by the state.
C programmers like OP literally want you dead. I would be "executed by the state" if these C programmers had any kind of power.
i code in C tho.
on a more serious note:
OP wouldnt do that.
but the world, including, or especially- the west; is rife with political violence.
and it isnt the "chuds" who are in power, are they?
>authoritarianism is good
Good goy
>there is nothing wrong with how C deals with strings
Spoken like a true LARPer
C'mon man, not even Makefiles under 100 lines? At least give us POSIX shell
no
Hobbyist thread.
> Using C
Skill issue, who needs more than asembly?
But the irony aside, use the language that fits the job. People that fail to acknowledge the benifits of python or rust in certain use cases are bad dev., Regardless how good they remeber syntax and the few algorithms/data structures.
>40 replies
>not a single person pointed out that asm and binary are literally the same thing
Classic IQfy nocoder thread
is this bait? ASM was considered high level when it was invented. It was invented to speed up the programming process.
It doesn't get compiled, it already is machine code, just in human readable form. It's like translating letters to numbers. 14 9 7 7 5 18
yeah.
but then wheres the cutoff for the concept of translation?
bc machine code isnt straight up executed either.
multithreading, predictive branching, out of order operations and latency hiding in a larger sense make it so that a program executes in the order of "whatever".
thats why defining the cutoff between translation and code generation is a valid question. there simply isnt a case where machine code translates to instructions 1:1 on modern hardware
(errata)
>mutlithreading
*hyperthreading
noep.
binary is machine code when asm is its readable form.
also, following your logic C == JS bc both are compiled into MC
(ps)
>js interpreted
you know what i mean
>nocoder
So I assume you've programmed in assembly, then? Actually learn an assembly language sometime and then you'll learn how different and easier to work with it is than even disassembled machine code.
I could never get anything productive done in ARM if I had to know three (3) instruction encodings.
OP here, sorry I meant to say if Pascal was adopted instead of C.
>no python, javascript, C#, rust, etc.
Take me there.
>make asm and c a requirement
>you can use a higher level language only after proving you can use those
>filter out pajeets and "coders"
>software quality improves 1,000x overnight
Why didn't we do this?
quality improves 1,000x overnight
Most of the software that sucks is written in C. Universities already force everyone to learn C and it just made software worse.
>os kernels
>all major sql databases
>game engines
>"Most of the software that sucks is written in C."
You're a moron.
>Universities already force everyone to learn C and it just made software worse.
They don't filter anyone on it. People just cheat and pass and move on anyway to produce 50 MB web pages that suck. Math also used to be a filter and they relaxed that to because "we need programmers."
i had to implement data structures right in assembly, filtered like 95% of the class
"sufficiently complicated C project" = anything bigger than FizzBuzz
>slow implementation of half of cargo
confusingly, they mean slow in absolute terms, but not relative to cargo
>any non-trivial Rust project links to C to get significant amount of work done
Only because C is a much older language. In a few years AI will port all that shit automatically and boomers will either mourn the end of C or seethe in denial.
Good bait.
two more weeks
Remove C, and it's true.
Please, for the love of god, provide your own original sample of anything you wrote in binary. When you admit that you don’t have anything to show, please delete this thread.
00001110 00001001 00000111 00000111 00000101 00010010
I read that shit instantly, I'm a binary haxor.
>train goes OVER your house
Nightmarish
>binary
I think you meant machine code, there is no "binary" language.
I'm still waiting for an optimizing assembler.
Not some bullshit "encoding optimization" or "actually just C", I want an actual optimizing assembler.
>optimizing assembler
I don't get it.
Neither does he.
None of you knew that "optimizing assemblers" were in fact a thing. Granted, they do only limited transformations since processor flags etc are global state and will escape subroutines but yeah every assembler wanted to be called "optimizing" in the sales text in like the 80s and 90s.
Thinly-veiled beginner thread
>If binary, ASM, and C were the only program --Segmentation Fault (core dumped) -- ACK!!!