The Makefile I use with JavaScript projects

Post by yoz-y » Thu, Mar 01, 2018, 9:29 AM UTC

gjvc wrote: post #82

yoz-y wrote: post #57

Earlier quoted context omitted.

cmake is good but it is quite heavily geared towards C/C++ development. I would love to have some modern makefile with a bit nicer syntax. Fitting into 80 columns is no longer a must.

In case you didn't know, the 80 column limitation has its origins here https://en.wikipedia.org/wiki/Punched_card#IBM_80-column_pun...

Post by jstimpfle » Thu, Mar 01, 2018, 9:36 AM UTC

jimktrains2 wrote: post #366

jstimpfle wrote: post #316

Earlier quoted context omitted.

C is a systems programming language. It doesn't have closures or other features from functional programming. In other words, you can't "create functions at runtime". That is why you basically never see a function returning another function.

So, go is also a "systems" language, so the terms more or less meaningless now. Assuming you mean a language we can easily compile to an independent binary capable of being run directly on a microprocessor with no support, I offer you rust as a counter-example. Also, functional programming and returning functions does not mean they are created at runtime.

Post by v_lisivka » Thu, Mar 01, 2018, 10:25 AM UTC

Spivak wrote: post #288

Chlorus wrote: post #238

Earlier quoted context omitted.

Almost every CLI program I've ever used in Windows has no problem with spaces in filenames, so I don't exactly why he's fixated on the GUI... But I had forgotten, computers aren't useful as tools to accomplish work, but as mechanisms to assuage intellectual inferiority complexes. He should advocate for punch cards again, since that would certainly stop morons from using computers.

Window and Linux shells have the same ideas about spaces in file names, which is that if they appear they need to be quoted or the space character needs to be escaped. Outside of Make which has long and boring historical reasons for not supporting spaces well, just about every program is fine with spaces.

Post by sureaboutthis » Thu, Mar 01, 2018, 10:47 AM UTC

com2kid wrote: post #216

hzhou321 wrote: post #198

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…

> And there are solutions. One solution, from those who don't code, seems to demand ("developers", paid or not) that every tool that deal with files should handle this additional complexity, regardless of their context and what they think. Users expect computers to work in a non-surprising ways. It isn't natural to use dashes or underscore in file names. Training users to be afraid of spaces is just teaching them one…

Post by josteink » Thu, Mar 01, 2018, 11:30 AM UTC

gkya wrote: post #363

neonscribe wrote: post #178

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…

Spaces in filenames create troubles with almost every command line tool. cut(1), awk(1), find(1), xargs(1), what not. How do you quote them, do you need to use \0 as a separator instead, do other commands on the pipeline support \0 separators? What happens after a couple expansions, passing stuff from one script to another? And what the heck happened on 31 dec 1999 that the world became a different place where sudden…