#1458: Don't add probed warnings to config information.
--------------------+-------------------------------------------------------
Reporter: coke | Owner:
Type: RFC | Status: new
Priority: normal | Milestone:
Component: none | Version: 2.1.0
Severity: medium | Keywords:
Lang: | Patch:
Platform: |
--------------------+-------------------------------------------------------
During configuration, all warnings that are successfully probed are
entered into the parrot configuration. So if you built with gcc, you can
run:
{{{
$ ./parrot_config -Wall
1
}}}
This seems like overkill, especially when:
{{{
./parrot_config ccwarn
}}}
seems sufficient. (ccwarn is empty in trunk, but what you'd expect in the
rm_cflags branch.)
Feedback (esp. whether or not this constitutes a deprecation issue)
welcome.
--
Ticket URL: <https://trac.parrot.org/parrot/ticket/1458>
Parrot <https://trac.parrot.org/parrot/>
Parrot Development
_______________________________________________
parrot-tickets mailing list
[email protected]
http://lists.parrot.org/mailman/listinfo/parrot-tickets
