[a / b / c / d / e / f / g / gif / h / hr / k / m / o / p / s / t / u / v / vg / vm / vmg / vr / vrpg / vst / w / wg] [i / ic] [r9k / s4s / vip] [cm / hm / lgbt / y] [3 / aco / adv / an / bant / biz / cgl / ck / co / diy / fa / fit / gd / hc / his / int / jp / lit / mlp / mu / n / news / out / po / pol / pw / qst / sci / soc / sp / tg / toy / trv / tv / vp / vt / wsg / wsr / x / xs] [Settings] [Search] [Mobile] [Home]
Board
Settings Mobile Home
/g/ - Technology


Thread archived.
You cannot reply anymore.


[Advertise on 4chan]


File: fine.png (16 KB, 1273x131)
16 KB PNG
>Made a thread here sharing my cool shell language
>>109216130
>PEOPLE WANT TO SEE WHAT'S BEHINDE
so here it is: https://files.catbox.moe/vqaucc.zip
(Propratiry software, all rights recived.)
>>
>>109224800
the code base looks very nice and clean
though writing your own sha256 function will make security nerds screech

in terms of usability I am going to throw myself out of a window if i have to type "list" for the 4th gorillion time. Theres a reason common commands are restricted to 2-3 letter things. Its not too bad but whatever. Also a shell primarily runs commands which do the actual work, your shell implements the command themselves which will get very headache inducing without some sort of general "protocol" outside of ExecResult. Unix chose binaries, processes, and pipes. Like a fully featured "ls" with all the options could take up half of the current line count of your shell and your not stuffing that in commands.c

It kinda reminds me of busybox, idk having a subfolder of commands so each command can stretch out a bit, and then having some abstraction or framework would be cool
>>
>>109225001
thanks for the feedback I guess
>>
>>109224800
> lainfag post
been a while since I've seen one of those guys outside of their gay retarded basement
> all rights reserved
it's already scraped and eaten by AI for china just like all github sausecode



[Advertise on 4chan]

Delete Post: [File Only] Style:
[Disable Mobile View / Use Desktop Site]

[Enable Mobile View / Use Mobile Site]

All trademarks and copyrights on this page are owned by their respective parties. Images uploaded are the responsibility of the Poster. Comments are owned by the Poster.