It's CPP not C

[Robert]

The BCX command line -c flag is counterintuitive and could be seen to be a part an obscurantist agenda.

The -c flag BCX is translating to a .cpp file not a .c file.

A -cpp flag added would help alleviate some cognitive dissonance. It could be added and the -c left as is for backwards compatability.

And of course, if you wanted to feed the needs of the with-it cognoscenti hipster, the flag could be -c++.

I think that even James Fuller would approve even though he seems to be a diehard advocate of inline $CPP.

[MrBcx]

I disagree with this suggestion and would argue that such a mod is unnecessary and a waste of time.

Anyone proclaiming to have any experience in programming but who cannot understand what -c
means given the list below is a !@#$%^& moron and should seek employment more in line with
their aptitude - say, at a tire shop or a fast-food chain. "Would you like fries with that McApple pie?"


BCX BASIC to C/C++ Translator (c) 1999 by Kevin Diggins
Version 7.4.5 (BETA)  Compiled with X86 Pelles C

 Usage: BC infile [.bas] [options]
 [-b] Build using user-defined bat file .. ex -b:c:\bat\pw.bat
[-c] Generate C++ Compatible code
 [-d] DEFINE a constant ... ex. BC MyFile -D:MyConst[=SomeValue]
 [-e] Write ERRORS to BCX.ERR file
 [-f] Output FILENAME... ex. BC MyFile -f:C:\MyFiles\MyFile.c
 [-h] Generate HEADER file for use with $Projects
 [-i] Send Warnings and Errors to INFOBOX
 [-k] KILL the generated BCX generated 'C' file
 [-l] Create Runtime LIBRARY source and header Files
 [-m] Enable embedded BCX Code in the C translation
 [-n] Enable NO RUNTIME Code Generation
 [-o] OUTPUT a copy of the generated C file to STDOUT
 [-q] QUIET - No output to screen during translation
 [-r] Update BCX Path variable in the Windows REGISTRY
 [-s] Show STATUS of translation by line number
 [-t] TURBO Mode ON w/optional size ... ex. BC MyFile -t[:1024]
 [-u] Turn UNICODE Support ON
 [-w] Enable WARNINGS during translation
 [-x] EXCLUDE Win32 Headers from the resulting C file
 [-z] ZAP (remove DEFAULT headers and libraries from the resulting C file

[Robert]

Anyone proclaiming to have any experience in programming but who cannot understand what -c
means given the list below is a !@#$%^& moron and should seek employment more in line with
their aptitude - say, at a tire shop or a fast-food chain. "Would you like fries with that McApple pie?"

Yeah well, you know, some of us couldn't pour water out of a boot with instructions on the bottom of the heel.