* Enable warnings

* Work without "-fpermissive" option

* Cosmetic fix

* Add "const" to fix warnings

These strings are not needs to modify.

* No need to use "#pragma once" in main C++ source file

* Cosmetic fix

Add newline to end

* Return nullptr if error

* delete() not works for "void*"

Cast specific type to use delete()

* Disable VC++ specific pragmas for other C++ compilers

* Fix warning

* Fix warning

* Use pipeline for compiler

* Enable code optimization

* Add "default:" to fix "switch" syntax warning

* Use "nullptr" for null pointer

* Use nullptr instead of NULL

* Use nullptr instead of NULL

* Use "L" notation for wide character

* Use C++ header instead of raw C header

Multi-byte I/O dose too match for text input in some locale.

For example, "," in numbers treat as decimal separator, not word separator.
This makes "1,234" as "1234", not "1" and "234".

Use "C.UTF-8" to avoid this problem.

* Use UTF-8 for multi-byte character I/O everywhare

This fix is required for "libstdc++".
Without this fix, "libstdc++" only works for 7bit ASCII.

It fixes https://github.com/microsoft/pict/issues/24 .

* Use current locale instead of fixed UTF-8 locale

It is good for non-UTF-8 (ANSI/OEM) encoding input.
Use environment variable "LANG" or "LC_CTYPE" to change input encoding.

(example)
$ LC_CTYPE="C.UTF-8" pict utf8-input.txt

* Add document for non-ASCII (UTF-8/ANSI) input encoding

From February 2021, in order to provide feedback on pull requests, Code Scanning workflows must be configured with both `push` and `pull_request` triggers. This is because Code Scanning compares the results from a pull request against the results for the base branch to tell you only what has changed between the two.

Early in the beta period we supported displaying results on pull requests for workflows with only `push` triggers, but have discontinued support as this proved to be less robust.

See https://docs.github.com/en/free-pro-team@latest/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning#scanning-pull-requests for more information on how best to configure your Code Scanning workflows.

* Create codeql-analysis.yml

* Rename the action