Follow Slashdot blog updates by subscribing to our blog RSS feed

 



Forgot your password?
typodupeerror

Comment Re:MenuChoice and HAM (1992) (Score 1) 268 268

The problem with shell scripts for this kind of thing is that they're a Turing-complete language. This makes it very hard to present to the user what they actually do. .BAT files on DOS / Windows provided that functionality too, but unless you aggressively restrict yourself to a subset of the shell language it's very hard to check a .sh / .bat file and see exactly what command is going to be invoked.

Comment Re:MenuChoice and HAM (1992) (Score 1) 268 268

This requires the program to be explicitly written that way. Gcc and clang also do this, to detect whether they're invoked as C or C++ compilers, and clang will detect a target triple if it's the compiler invocation name prefix. This just goes in argv[0] though - you can't modify the other arguments from a shortcut. It would be really useful to be able to add things like --sysroot=/some/path and -msoft-float to a symlink so that you had a single cc that you could invoke as a cross compiler, but currently the only way to do this is with a tiny shell script that execs the compiler with the correct flags.

Comment Does not follow (Score 1) 215 215

Premiums will necessarily drop? What planet do you live on where prices go DOWN? With the great exception of the computer industry, prices are almost always sticky to the upside. Seriously insurance companies would not be so foolish as to price themselves out of the market.

Comment Re:awkward! (Score 1) 180 180

Nonsense. It is true, however, that Windows and Linux use different (overlapping) subsets of the SATA (and SCSI) command sets and, in particular, use very different sequences of commands in common use. If you test heavily with Windows and not with Linux, then you may find that there are code paths in your firmware that Linux uses a lot but which are mostly untested.

Radioactive cats have 18 half-lives.

Working...