summaryrefslogtreecommitdiff
path: root/development/check
diff options
context:
space:
mode:
authordsomero <xgizzmo@slackbuilds.org>2013-11-22 02:29:22 -0500
committerdsomero <xgizzmo@slackbuilds.org>2013-11-22 02:29:22 -0500
commit610e8461bb9b201adbd4bd9257a9bf48be71f62b (patch)
tree6ca569349369dbaa4ba6c24795d6201303b9d2fa /development/check
parent8fe2e3d82e774b981c041e043ca2f71ed672b493 (diff)
downloadslackbuilds-610e8461bb9b201adbd4bd9257a9bf48be71f62b.tar.gz
various: Fix slack-desc formatting and comment nit picks.
Signed-off-by: dsomero <xgizzmo@slackbuilds.org>
Diffstat (limited to 'development/check')
-rw-r--r--development/check/slack-desc18
1 files changed, 9 insertions, 9 deletions
diff --git a/development/check/slack-desc b/development/check/slack-desc
index 14d096f6db..4f7235208f 100644
--- a/development/check/slack-desc
+++ b/development/check/slack-desc
@@ -1,18 +1,18 @@
# HOW TO EDIT THIS FILE:
-# The "handy ruler" below makes it easier to edit a package description. Line
-# up the first '|' above the ':' following the base package name, and the '|'
-# on the right side marks the last column you can put a character in. You must
-# make exactly 11 lines for the formatting to be correct. It's also
-# customary to leave one space after the ':'.
+# The "handy ruler" below makes it easier to edit a package description.
+# Line up the first '|' above the ':' following the base package name, and
+# the '|' on the right side marks the last column you can put a character in.
+# You must make exactly 11 lines for the formatting to be correct. It's also
+# customary to leave one space after the ':' except on otherwise blank lines.
|-----handy-ruler------------------------------------------------------|
check: Check (unit test framework)
check:
check: Check is a unit test framework for C. It features a simple interface
-check: for defining unit tests, putting little in the way of the developer.
-check: Tests are run in a separate address space, so Check can catch both
-check: assertion failures and code errors that cause segmentation faults or
-check: other signals. The output from unit tests can be used within source
+check: for defining unit tests, putting little in the way of the developer.
+check: Tests are run in a separate address space, so Check can catch both
+check: assertion failures and code errors that cause segmentation faults or
+check: other signals. The output from unit tests can be used within source
check: code editors and IDEs.
check:
check: See http://check.sf.net for information and tutorial.