--help flag produces no output

[MaddyGuthridge]

Currently, it appears that running dcc --help produces no output.

Tested on:

• CSE: dcc version 2.37
• Built from source on latest commit 0a888fd

Based on a git bisect, the bad commit appears to be ea445a0

[Dylan-Brotherston]

This is apparently intentional

dcc/compile_time_python/options.py

Lines 390 to 392 in 0a888fd

	elif arg == "--help":
	print()
	sys.exit(0)

[Dylan-Brotherston]

actually it looks like to was deleted in a refactor here:
ea445a0#diff-334d1bf3e930817dcd2334b26ba42eb1bf5e8cfa419afeb7b02164a319eee42cL754

dcc/compile_time_python/compile.py

Lines 754 to 773 in b195f98

	elif arg == "--help":
	print(
	"""
	-fsanitize=<sanitizer1,sanitizer2> run two sanitizers (default -fsanitize=address,valgrind)
	The second sanitizer is a separate process.
	The synchronisation of the 2 processes should be effective for most
	use of the standard C library and hence should work for novice programmers.
	If synchronisation is lost the 2nd sanitizer terminates silently.
	-fsanitize=<sanitizer> check for runtime errors using using a single sanitizer which can be one of
	address - AddressSanitizer, invalid memory operations
	valgrind - valgrind, primarily uninitialized variables
	memory - MemorySanitizer, primarily uninitialized variables
	--leak-check check for memory leaks, requires --fsanitizer=valgrind to intercept errors
	--no-explanations do not add explanations to compile-time error messages
	--no-shared-libasan do not use libasan
	--ifdef use ifdef instead of ld's -wrap option
	"""
	)
	sys.exit(0)

[MaddyGuthridge]

I wonder if using a dependency such as click or the (worse) stdlib argparse module for argument-parsing to ensure all these options are documented and autogenerate a --help option would be worthwhile...