Remove unnecesary spaces
This commit is contained in:
parent
81a3f2f76c
commit
9bfcdc8655
@ -177,6 +177,29 @@ int main(int argc, char *argv[])
|
||||
// .rfx files contain sampleRate, sampleSize and channels information
|
||||
if (argc > 1)
|
||||
{
|
||||
// TODO: Support config args parameters: -hz 44100 -bit 16
|
||||
/*
|
||||
-? | -h — print help for command-line parameters.
|
||||
-c file — use an alternative configuration file instead of a default file.
|
||||
-v — print nginx version.
|
||||
-V — print nginx version, compiler version, and configure parameters.
|
||||
-s signal — send a signal to the master process.
|
||||
|
||||
//http://stackoverflow.com/questions/15683347/when-implementing-command-line-flags-should-i-prefix-with-a-fowardslash-or
|
||||
Windows convention seems to prefer the use of the forward slash ipconfig /all
|
||||
Unix convention seems to prefer the hyphen -v for single-letter parameters,
|
||||
and double hyphen --verbose for multi-letter parameters.
|
||||
|
||||
I tend to prefer hyphens, as they are more OS-agnostic (forward slashes are
|
||||
path delimiters in some OSes) and used in more modern Windows apps
|
||||
|
||||
One reason for continuing to use the single letter options is because they can be strung together:
|
||||
ls -ltr is a lot easier to type than ls --format=long --sort=time --reverse
|
||||
|
||||
sample:
|
||||
PVRTexTool -i tex_Natural_A.tga -o tex_Natural_A.pvr -f PVRTC1_2,UBN,lRGB -q pvrtcfast -legacypvr
|
||||
*/
|
||||
|
||||
for (int i = 1; i < argc; i++)
|
||||
{
|
||||
if ((strcmp(GetExtension(argv[i]), "rfx") == 0) ||
|
||||
|
Loading…
x
Reference in New Issue
Block a user