491–500 of 525 posts
Earlier quoted context omitted.
You do, since different communities use different build tools. And they even switch tools, for the new kid on the block.
Bullshit. You're arguing as if every JS developer has to interact with every JS community. Stop presenting these ridiculous false dichotomies.
Earlier quoted context omitted.
> "Basically, it’s used everywhere that C is used and then some." It's the other way around. Every JavaScript program is run by a C/C++ program.
But if you consider browsers to be a "platform", which I think they are in fairness, then the GP comment could still apply. Whether the browser is written in C is pretty irrelevant to whether it can host it.
Earlier quoted context omitted.
I was able to to it. Here's the source code "hello world.c": #include int main(void) { puts("Hello, world!"); return 0; } And here's the minimal Makefile to generate the output: hello world: Of course, I did have to swap out the ASCII SP (character 32) for the Unicode non-blank space (code 160) to get this to work, but hey, spaces!
>I did have to swap out the ASCII SP (character 32) for the Unicode non-blank space (code 160) How? EDIT: Ok, now I got it. Boy that was a wild ride.
Edit: rewording and typos.
Earlier quoted context omitted.
Simple makefiles couldn't be more simple. task: dependency list of commands That's about as easy as it gets.
Real world makefiles are not simple like this. The simplest makefile I can think of is still hundreds of lines long: https://git.musl-libc.org/cgit/musl/tree/Makefile
Earlier quoted context omitted.
Pffffft. Nobody wants to touch C these days. That's why many, many, many, many, many more people are writing server, browser, desktop and mobile apps with JS and not C.
https://www.tiobe.com/tiobe-index/
Earlier quoted context omitted.
>I did have to swap out the ASCII SP (character 32) for the Unicode non-blank space (code 160) How? EDIT: Ok, now I got it. Boy that was a wild ride.
I did not do the method below. Instead, I wrote a script to generate the filename with the non-breaking space where I needed it. Edit: rewording and typos.
Earlier quoted context omitted.
Demanding the support of spaces in filenames significantly complicates code as simple space delimination no longer works and other delimination schemes are much more error prone -- forgetting balancing quotes, any one? While you are allowing spaces, you probabaly are allowing all possible code points or maybe even a null byte? Thinking about it gives me headaches. I hate hearing people using 21st century or modern as…
> The merits of filenames with spaces is they read better in a GUI explorer. Even this merit is debatable. Is foo bar two things or one? I know foo-bar is one.
It all depend of domain convention. Make align on variable naming convention .. that is all
Earlier quoted context omitted.
I did not do the method below. Instead, I wrote a script to generate the filename with the non-breaking space where I needed it. Edit: rewording and typos.
Any way I can see the script? Looks like I am still learning and ended up taking a longer route.
h = "hello" .. utf8.char(160) .. "world"
f = io.open("Makefile","w")
f:write(h,":\n")
f:close()
f = io.open(h .. ".c","w")
f:write([[
#include
int main(void)
{
puts("Hello, world!");
return 0;
}
]])
f:close()
Earlier quoted context omitted.
https://www.tiobe.com/tiobe-index/
http://githut.info/
The TIOBE index, while not entirely accurate either, does reflect usage by a much more broad set of engineers.
I used make heavily in the 80s and 90s, but haven't much since then. Recently I started a project that had source files getting processed into PDF files, for use by humans. Since this is the 21st century, those files have spaces in their names. At a certain point, I realized that I should be managing this processing somehow, so I thought of using a simple Makefile. A little searching reveals that the consensus on usi…
Demanding the support of spaces in filenames significantly complicates code as simple space delimination no longer works and other delimination schemes are much more error prone -- forgetting balancing quotes, any one? While you are allowing spaces, you probabaly are allowing all possible code points or maybe even a null byte? Thinking about it gives me headaches. I hate hearing people using 21st century or modern as…
I've even worked with variables with spaces and special characters.
I don't see why filenames are so much more special, except a lot of old tools never got updated to world beyond ASCII