/tech/ - Technology★

foo (
bar
)

>>872053 (OP)

(foo bar)

foo bar

Any language worth its salt doesn't require parens around function calls.

Which is it?

foo; bar; baz;

or

foo; bar; baz

hint: the semicolon is a binary operator

(foo)bar

>>872067

C was a mistake

>>872053 (OP)

int foo
(
<tab> int bar
)
{
... function body... 
} 

foo < bar

>>872053 (OP)

foo {

bar

};

>>872075

That's not C, the semicolon is not an operator in C.

>>872080

It should have been.

 foo bar 

In OCaml those parentheses could be omitted.

>>872080

Isn't comma an operator in C tho?

foo.bar();

(foo (bar baz))

>>872087

No

foo->bar();

op (fag )

>>872053 (OP)

foo(bar){
    like_this();
}

        **** COMMODORE 64 BASIC V2 **** 
       64K RAM SYSTEM 38911 BASIC BYTES FREE

READY.
10 FOO$
20 BAR$
30 PRINT FOOBAR

>>872053 (OP)

foo (((bar)))

	{
		baz ;
	}
 ( bar ) foo ;

>>872053 (OP)

foo[ bar; ];

been dabbling in inform 6 lately

BAR FOO

>>872053 (OP)

Function definition:

int foo(bar)
{
     ...
}

For statement:

for (i = 0; i < bar; ++i) {
    ...
}

>>872413

barefoot?

>>872067

>the semicolon is a binary operator

No, it's not an operator at all. It's just punctuation (statement termination delimiter, to be specific).

>>872127

>there's no comma operator in C

Wrong, there is one. Not every comma in C code is the comma operator though (the commas separating functions parameters aren't as they are punctuation similar to the semicolon, while the commas in a for statement are).

(self.foo)(
    bar,
);

>foo bar

FUNCALL "{\"function\":\"foo\",\"argList\":[{\"varName\":\"bar\"}]}"

lol u take him 2 da foo bar|

int
/** Brief description.
 * Detailed description.
 * @param a The first parameter
 * @param b The second parameter
 * @return The result
 */
foo(int a, int b) {
    if (a != b)
        return a%b;

    if (a + b == 2) {
        b = a + 2;
        a %= b;
    }
    bar(a, b);
    while (a < b) {
        a = baz(a, b);
        quux(b, a);
    }

    return a*14730;
}

TL;DR documentation between return type and signature, function calls and declarations have no space between ident and parens, if/while/switch (keywords) have a space before the paren, Java-style braces.

>>872053 (OP)

its

>foo bar

$::foo bar.

>>872053 (OP)

bar @ foo

>>872067

foo, bar, baz.

>>872629

>his whitespace has side effects

oh no where are your endofunctors now

>>872632

[code] int foo, bar, baz;

>>872666

[code] int foo, bar, baz;[code]

>>872666

>>872667

goddammit how do I write code?

>>872668

 kode with karlie 

>>872669

add a slash before the second code

>>872669

how do I use [code] tag?

[code] syntax plox

>>872672

>add a slash before the second code

that was my next guess.

 int foo, bar, baz; 

>>872467

What?

>>872680

#include <stdio.h>

int main()
{
    char input;

    printf("Please input characters: ");
    scanf("%[?]", input);

    if (input == 'BAR FOO') {
        puts("Did you say \"barefoot\"?");
        puts("Because if you say \"BAR FOO\" five times fast"); 
        puts("it sure af sounds like \"barefoot\"!"); 
    }
    return 0;
}

I just realize I don't know how to do character inputs yet because I haven't gotten that far in the book :-(

>>872698

I was writing in FORTH. FOO would have stack effect ( x -- x') and BAR is what would be operated on

>>872707

>FORTH

interesting. I hadn't heard of that language until now. May I ask why? I mean, it seems like an obscure language, so I'd be interested to know why you decided to learn it.

I'm trudging through C right now. In a couple years, I'll be another wannabe programmer fluent in a language or two working in a coffee shop, is my guess. Kinda depressing, but I've got to give it a shot. I'm really starting to wonder whether I would want to do this for a job, though. I think I'd rather do server maintenance than code... I think. I guess I just can't imagine what the actual job would be like at this point.

>>872708

should've seen that coming...

There's a unifying theme to a lot of my Haskell style, and it is this: be explicit and use names. Why pervasively use record fields? I'm being explicit about the purpose of those pieces of data by giving those fields a name. Why qualify imports? I'm being explicit about their provenance by giving their provenance a name. Why use functions or records of functions instead of typeclasses? I'm being explicit about what functionality I'm dispatching to by giving that functionality a name. A related theme is: optimize for reading code later. If it takes longer to write or uses more lines or more variable names, but it's going to be clearer to another person reading my code---or to me, coming back to that source file in a month or a year—I will absolutely take the time to write the longer code.

But also, like a mediocre high-school essay writer, I want to reiterate what I wrote at the beginning: this is one of many styles, and it has its own tradeoffs! (Verbosity being a big one here.) Your style might be (and probably is) different, and that's a good thing: in fact, I'd be interested in reading analogous posts to this one that describe the specifics of and motivation for other people's Haskell styles! I don't think there's a "wrong way" to write Haskell: there's a multiplicity of possibilities, and we as Haskell users should embrace that!

…well, unless y'all use TypeInType, in which case you're clearly depraved in ways that medical science cannot fix.

>>872711

Cause programming is fun and Forth is fun. And it's way more powerful than C and the gang, just lacking in libraries (especially now it's basically dead). I write my own scripts in a dialect called Retro Forth

>>872536

>user was banned for this post

>>872053 (OP)

Neither. It's

foo(bar);

/thread

>>872711

>FORTH

Because it's machine-code level of abstraction. If your other option is using assembly - FORTH might be a more productive choice. If your other option is BASIC - FORTH is only correct choice. If you have something as fancy as C compiler on your platform - you are out of FORTH use case.

For fun/educational purposes, write FORTH VM. It's simple enough that you can make decent one in one evening. Then write for it.

-[--->+<]>-.[---->+++++<]>-.---.--[--->+<]>-.++[->+++<]>+.------.++++++++++++.--------.[->+++<]>-.

>>872815

>>873200

well, I'm just 1wk/4ch into C programming. I went with it because it seemed like the most useful place to start and the best for the job market. I won't have a CS and I'm not sure how to get experience in the field, though, so idk if I'll ever get a job. I have degrees, just not in CS. trying to make a career switch

>>873221

you could start by doing a poo in the loo pajeet

>>873235

If I were a pajeet. I wouldn't have lost my career for being le ebul wyt mail blonde nazi jewkiller cishet patriarchal rape culturist

>>872053 (OP)

Trick question. People who waste time on this bullshit instead of fixing the real problems in their code are unemployable.

>>873273

>not adhering to a code style that is both sane and consistent is not a real problem

>>873365

Your format should follow the convention set by the lead developer. This is a trivial problem for your code formatting software. This is the reason why it's meaningless to think about formatting beyond what the lead developer says.

>>873200

FORTH is more productive for most software, once you think outside the C-like mindset.

>>873221

Learn C++ if you want a job.

foo(bar)

bar foo .

>>872053 (OP)

foo
(
    bar
)

>>872572

>/.*java.*/i

<REEEEEEEEEE REEEEEEEEEEE JAVA JAVA JAVA GTFO PAJEEET REEEEEEEEEEEEEEE

I want /g/ to backsodus.

>>872698

This should give you the functionality without any buffer overflows (although I could be wrong since I'm still a C scrub)

#include <stdio.h>
#define BUFFER_SIZE 10
#define BAR_FOO_STR "BAR FOO"

int main()
{
    char input[BUFFER_SIZE];

    printf("Please input characters: ");
    if (fgets(input, BUFFER_SIZE, stdin) != NULL && strlen(BAR_FOO_STR) == strnlen(input, BUFFER_SIZE) && strncmp(input, BAR_FOO_STR, BUFFER_SIZE) == 0)
    {
        printf("Did you say \"barefoot\"?");
        printf("Because if you say \"BAR FOO\" five times fast"); 
        printf("it sure af sounds like \"barefoot\"!"); 
    }
    return 0;
}

>>872711

Look up the history of the CRPG "Starflight" (published by Electronic Arts on 1989). Forth is good for making smallest compact code. Very usedul for microcontrollers and such.

>>875623

Just use readline(3).

>>876136

Sounds like dependency bloat for something so simple.

How do you faggots ever get any work done if you squabble over the pettiest shit like fucking intervals between brackets?

>>876144

It's as if they've never heard of code formatting programs.

 xd 

>>872468

Oh yeah, you're right, forgot about the for loop comma

>>872144

Best method.

>>875605

>I want /g/ to backsodus

Agreed. Pack your things and leave, Javanigger.

type foo(bar, baz)
type bar;
type baz;
{
  return baz;
}

.section .data
op:
.ascii "fag"

.section .text
.globl func
.type func, @function
func:
movl $4, %eax
movl $1, %ebx
movl $op, %ecx
movl $3, %edx
int $0x80