* fix: Exit gracefully instead of panicking when trying to use features
* removed an unnecessary empty line
* Added logging of any errors encountered writing to stderr.
* only add regular files to path list
This fixes multiple issues. Before this commit, a directory with
a known file extension in its name would be added to the list of
"files" to open and read from. Another issue occurred with broken
symbolic links being added to the files list.
* add test to ensure directories not treated as file
* replace `unwrap()` with `rs_error!`
Modification on comments:
Batch - Add ::
Lisp - Comments can be nested (www.rosettacode.org/wiki/Comments#Common_Lisp)
Python - Reverted to hash, based on comment thread from pull #59 as
string has a return value
Changes to the quotes
Assembly - Uses ' ' or " "
Bash - Uses ' ' or " "
Batch - They don't use quotes for strings
Cold Fusion - Uses ' ' or " "
D - Uses " " or
Dart - Uses " " or ' ' or """ """ or ''' '''
Forth - Uses " " but new, doesn't have a preset
Fortrans - Use " " or ' '
Idris - Uses " " or """ """
Julia - Uses " " or """ """
Kotlin - Uses " " or """ """
Moustache - Uses " " or ' '
Nim - Uses " " or """ """
Pascal - Uses ' '
Perl - Uses " " or ' '
Php - Uses " " or ' '
Python - Uses " " or ' ' or """ """ or ''' '''
Ruby - Uses " " or ' '
Sass - Uses " " or ' '
Sql - Uses ' '
Toml - Uses " " or ' ' or """ """ or ''' '''
Typescript - Uses " " or ' ' or
Vimscript - Uses " " or ' '
Yaml - Uses " " or ' '
Zsh - Uses " " or ' '
* Made a series of modifications to the comments:
Clojure - Removed #
Forth - ( Comment) style comments need a space after the opening paren
Haskell - Has nested comments
Idris - Has nested comments
Jai - Has nested block comments
Julia - Has nested block comments
Kotlin - Has nested block comments
Pascal - Pascal should be multiline from { or (* to } or *)
Perl - Perl5 and earlier for multiline comments need =pod to =cut.
Python - Python can use """ or ''' for comments
Swift - Has nested block comments
I'm not entirely happy with the wording but wanted to avoid using terms like “match” to avoid giving the impression that things like regular expressions or shell globs were supported.