The most expensive coding font for free?
61–70 of 120 posts
Re: The most expensive coding font for free?
#62Re: The most expensive coding font for free?
#63Earlier quoted context omitted.
wait... what wrong with "} else {" ? It provides a simple and easy grouping of blocks.
This is obviously personal preference and opinion and all of that, but that's the whole point of discussion, so: if (something) { something(); } else { something_else(); } vs. if (something) { something(); } else { something_else(); } To me, the first one is chaotic. It's not so bad like that, but throw in a loop (as well as the external function declaration) and it's a complete mess. The second one is orderly. Block…
Re: The most expensive coding font for free?
#64Earlier quoted context omitted.
wait... what wrong with "} else {" ? It provides a simple and easy grouping of blocks.
This is obviously personal preference and opinion and all of that, but that's the whole point of discussion, so: if (something) { something(); } else { something_else(); } vs. if (something) { something(); } else { something_else(); } To me, the first one is chaotic. It's not so bad like that, but throw in a loop (as well as the external function declaration) and it's a complete mess. The second one is orderly. Block…
I agree with your points for functions, (most)loops, switches, and so in, but for if/else try/catch/finally do/while an other multiblock statements, I think it helps to have some convention to group them, other than indent level. The blocks depend on each other, not just are in proximity.
I would never do:
for (a;b();a++) {
stuff();
} if (test) {
...
}
because the if and the for are not parts of the same logical chunk. Nor would I do: ...
} else {
catchall();
} if (new_test()) {
...
Again because a new if is new logical chunk.Basically, it isn't about block delineation or about vertical space, its about grouping logical units that have multiple blocks at the same nesting level.
Re: The most expensive coding font for free?
#65Earlier quoted context omitted.
This is obviously personal preference and opinion and all of that, but that's the whole point of discussion, so: if (something) { something(); } else { something_else(); } vs. if (something) { something(); } else { something_else(); } To me, the first one is chaotic. It's not so bad like that, but throw in a loop (as well as the external function declaration) and it's a complete mess. The second one is orderly. Block…
But then you write int* foo, bar; and the troubles begin...
Meaning:
int* foo = whatever;
// do some stuff with foo, now we need bar
int* bar = whatever;
Outside of a for loop, I would never do two assignments on the same line, so it isn't an issue.If it really has to be done like that, I just suck it up in that case. C has its warts.
Re: The most expensive coding font for free?
#66Earlier quoted context omitted.
I'd be considering avoidance too if I had to give just under half of everything I make to the government. *edit And there are perfectly legal ways to reduce your tax burden. The point I'm laboring so hard to make here is that it's an absurd tax rate.
Indeed. And then you'd gladly take advantage of the social safety net if you became unemployed, or upon retirement, and of the roads the government built, and of the safety the police provides, etc. Not paying taxes is great if you don't cost the government anything. All of a sudden, though, when you want the services but don't want to pay for them, you become the leech that people keep accusing the poor of being. Yo…
And guess what? People recognize that. And when people think they're being jerked around..
Re: The most expensive coding font for free?
#67Earlier quoted context omitted.
If by broken you mean a catastrophic cultural failure to acknowledge that you should pay your taxes, and a resultant lack of enforcement, then yes.
I'd be considering avoidance too if I had to give just under half of everything I make to the government. *edit And there are perfectly legal ways to reduce your tax burden. The point I'm laboring so hard to make here is that it's an absurd tax rate.
Re: The most expensive coding font for free?
#68Earlier quoted context omitted.
Dude, you are distrustful... it's not the case: I'm at the 50% of the work with PragmataPro, anyone can realize it just by looking at the screenshots. If I wanted to escape with the loot I would not be so stupid to draw about 1600 glyphs spending 3 years of my life. Revenue from sales of licenses are not sufficient to cover even 10% of the time I used to arrive here. Then came the piracy that has stopped the sales. M…
"Appropriate" reward would be the reward the market decides you get, not what you hope for.
Re: The most expensive coding font for free?
#69Why is it so narrow? It reminds me of doing things like "} else {" in code, packing lots of content onto the screen and removing all readability.
There are two opposing schools: One (your?) school says readability is promoted by having as much visible structure as possible . The other (mine!) says readability is promoted by having as much visible context at the same time, as long as the structure is apparent. so instead of if (test1) { do_something1(); } else { do_something2(); } I write if (test1) do_something1(); else do_something2(); 4 times as much context…
I just didn't want to write a bunch of nonsense code as an example.
Re: The most expensive coding font for free?
#70Earlier quoted context omitted.
This is obviously personal preference and opinion and all of that, but that's the whole point of discussion, so: if (something) { something(); } else { something_else(); } vs. if (something) { something(); } else { something_else(); } To me, the first one is chaotic. It's not so bad like that, but throw in a loop (as well as the external function declaration) and it's a complete mess. The second one is orderly. Block…
But then you write int* foo, bar; and the troubles begin...