Huffmanashi No Naku Koro Ni

int kod(int *cnts, int i, int *j, int *k, int nsyms) {
int r;
if(*k > nsyms || i > *j && cnts[*j] < cnts[*k]) {
r = cnts[*j];
cnts[(*j)++] = i;
} else
r = cnts[(*k)++];
return r;
}

int huff(int *cnts, int nsyms) {
int i = 0, j = 0, k = 0;
for(i=0;i<nsyms-1;i++)
cnts[i] = kod(cnts, i, &j, &k, nsyms) + kod(cnts, i, &j, &k, nsyms);
cnts[i] = 2;
j = i-1;
k = j;
while(k) {
while(j > 0 && cnts[j-1] >= k)
j--;
cnts[i--] -= k - j;
cnts[i] = (k - j)*2;
k = j;
}
return nsyms - i;
}

>>40
I don't see how that's going to fix capitalism.

I don't see how that's going to implement diff

>>32
I don't think you understand the purpose of indentation very well.
You might think it's meaningless and have learned to get used to it, but at a glance, looking at your code to find something and identify structures becomes difficult. Then when others start reading your code they too will find it very hard to read compared to others' code.

Sure they can run ident(1), but are there really many notable benefits to foregoing indentation? All I can think of is saving file size, but that's a poor argument. Formatting your code should be an effortless part on yourself, and doesn't require you to be a ``code artisan'' to accomplish. Just think of how many people who looked at your code for 5 seconds and in the end just thought you are an amateur Apper without analyzing your techniques indepth.

So don't think it will only affect you. With almost all code people see being well formatted, it's hard to think they'll be ok with formatting some guy's code themselves just because he is kinda narcissistic.

>>43
This. dubs.

>>43
Benefits of not joining the indentation cult:
1.Lower file sizes
2.More data fits on one screen "The visual field is a scarce UI commodity"
3.Code doesn't get mangled due text filters and processing(indented code like python suffers from it well).
4.Its faster to read:
Reading indented code requires more scrolling and mental processing(comparing visual indentation with logical structure).
5.Its faster to write:
Without superficial indentation rules and policies, code writing naturally flows at the speed of typing out mental concepts(aids "Flow state"). No spacing, no indentation, no distraction: focus is always on code and not the aesthetic form it takes.
6.Its easier to debug:
Indented code error bring little context, often only a single statement.
Non-indented code errors show up as blocks of code.
7.Its terse structure allow to keep more of code in mind at the same time:with indented code you can't see it all due #2

>>45

Its faster to read
Its easier to debug

Nigga u dum

Added
http://void.wikidot.com/benefits-of-not-joining-the-indentation-cult

http://void.wikidot.com/one-man-fight-against-the-gay-lisp-menace
http://void.wikidot.com/why-basic-is-the-ultimate-language
http://void.wikidot.com/java-programmers-stole-my-bike

>>46
it's FV, what did you expect? he doesn't work on anything big and complex, he's just experimenting with pre-processor macros for fun. you don't need indentation to hack together an apply macro therefore it's useless for FV. the same goes for version control.

>>45
Consider the following: An excerpt of anoncoreutils, with indentation modified to mimic your ``Apping'' style. Can you understand how it works and what it does in 10 seconds?

#include <stdio.h>
#include <string.h>

int main(int argc, char **argv) {
int i;
if(argc!=2) {
fprintf(stderr,"usage: %s string\n",argv[0]);
return 1;
}
if(!strcmp(argv[1],"//"))
goto step_6;
if(!argv[1][0])
goto single_dot;
for(i=0;i<strlen(argv[1]);i++)
if(argv[1][i]!='/')
goto notslash;
goto single_slash;
notslash:
for(i=strlen(argv[1])-1;argv[1][i]=='/';i--)
argv[1][i]=0;
if(strrchr(argv[1],'/')) {
for(i=strlen(argv[1])-1;argv[1][i]&&argv[1][i]!='/';i--)
argv[1][i]=0;
step_6:
for(i=strlen(argv[1])-1;argv[1][i]&&argv[1][i]=='/';i--)
argv[1][i]=0;
if(argv[1][0])
printf("%s\n",argv[1]);
else
single_slash: printf("/\n");
} else
single_dot:
printf(".\n");
return 0;
}

>>50
Looks fine to me

>>50 Thats a waste of space
#include <stdio.h>
#include <string.h>
int main(int argc,char**argv){int i;
if(argc!=2){fprintf(stderr,"usage: %s string\n",argv[0]);return 1;}
if(!strcmp(argv[1],"//")){goto step_6;};
if(!argv[1][0]){goto single_dot;}
for(i=0;i<strlen(argv[1]);i++){if(argv[1][i]!='/')goto notslash;}
goto single_slash;notslash:for(i=strlen(argv[1])-1;argv[1][i]=='/';i--){argv[1][i]=0;}
if(strrchr(argv[1],'/')){for(i=strlen(argv[1])-1;argv[1][i]&&argv[1][i]!='/';i--){argv[1][i]=0;};
step_6:for(i=strlen(argv[1])-1;argv[1][i]&&argv[1][i]=='/';i--){argv[1][i]=0;}
if(argv[1][0]){printf("%s\n",argv[1]);}else{single_slash: printf("/\n");}}else{single_dot:printf(".\n");};return 0;}


>>52
Yeah this looks more like his style but without the syntax highlighting

Added line height for clarity for those who can't distinguish lines.

#include <stdio.h>

#include <string.h>

int main(int argc,char**argv){int i;

if(argc!=2){fprintf(stderr,"usage: %s string\n",argv[0]);return 1;}

if(!strcmp(argv[1],"//")){goto step_6;};

if(!argv[1][0]){goto single_dot;}

for(i=0;i<strlen(argv[1]);i++){if(argv[1][i]!='/')goto notslash;}

goto single_slash;notslash:for(i=strlen(argv[1])-1;argv[1][i]=='/';i--){argv[1][i]=0;}

if(strrchr(argv[1],'/')){for(i=strlen(argv[1])-1;argv[1][i]&&argv[1][i]!='/';i--){argv[1][i]=0;};

step_6:for(i=strlen(argv[1])-1;argv[1][i]&&argv[1][i]=='/';i--){argv[1][i]=0;}

if(argv[1][0]){printf("%s\n",argv[1]);}else{single_slash: printf("/\n");}

}else{single_dot:printf(".\n");};return 0;}


indent
those
dubs

>>45

Its faster to read
Its easier to debug

Weird how these are also the arguments for using indentation.
Really makes you think.

>>56
What is faster to read, 10 lines of text or 40 lines?

>>57
1. strip all newlines
2. paste code into Microsoft Notepad
3. turn off word wrapping

congratulations! you now have one line of text, which will be THE FASTEST to read

>>57
Well it's true that 10 lines would be faster to read, then.
Not faster to understand, though.

This is quicksort in APL
Q←{1≥≢⍵:⍵ ⋄ S←{⍺⌿⍨⍺ ⍺⍺ ⍵} ⋄ ⍵((∇<S)⍪=S⍪(∇>S))⍵⌷⍨?≢⍵}

>>59
..due a lack of mental capacity.

>>61
Say whatever you want, FrozenAnus. It doesn't make it true.

>>61
is this right? >>49

>>63
C macros is only one of my interests. They're probably well known because i like to showcase theoretical stuff from the void.h/void2 headers. I don't actually write programs composed from macros, unless its a demo thing.

>>64
>I don't actually write programs
Knew it

>>65
Well. Its partially correct.
I don't write "programs" i write apps or utilities. Writing big projects and committing to support them isn't for me.
I prefer to use my time rationally, not being an open source code monkey. see http://void.wikidot.com/effort-reward-curve

Write programs that do one thing and do it well.
Write programs to work together.
Write programs to handle text streams, because that is a universal interface.

>>66
then stop shitting on things that help immensely when writing big programs.

>>68
>big programs
1./prog/riders didn't write anything big(20K+ line of code)
2.Big programs are usually split into small modules.
3.The only case where this could be useful is some huge file like sqlite source amalgamation(which is never edited manually).

>>69
Big programs are anything above 15 lines, thanks

Never argue with stupid people, they will drag you down to their level and then beat you with experience.

>>70

log10(LOC) Type
9+ Enterprise-Class
8-9 Enormous
7-8 Gigantic
6-7 Huge
5-6 Large
4-5 Medium
3-4 Small
2-3 Tiny
1-2 Extra Tiny


>>60
Needs to be replaced by emoji and APL will become popular overnight.

>>73
http://www.emojicode.org/

>>72
Google confirmed as Enterprise-Class
https://www.wired.com/2015/09/google-2-billion-lines-codeand-one-place/

>It's estimated that there are 111 billion lines of new software code generated by developers every year,
If they didn't indent the number would be much smaller.

>>76

If they didn't indent the number would be much smaller.

Retard.

>>76
indent
verb

ɪnˈdɛnt/

Start (a line of text) or position (a block of text) further from the margin than the main part of the text.
``type a paragraph of text and indent the first line''

synonyms: move to the right, move further from the margin, start in from the margin.
``the first line of a paragraph is indented by using the tab key''

>>66
An Apper
Wow!

>>77,78
Someone salty about their bloated indentation wasting space.