blob: f61f4c08b00c65fad3312d41931ab116e7fb0022 (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
|
# -*- tcl -*- base64.pcx
# Syntax of the commands provided by package base64.
#
# For use by TclDevKit's static syntax checker.
# See http://www.activestate.com/solutions/tcl/
# See http://aspn.activestate.com/ASPN/docs/Tcl_Dev_Kit/4.0/Checker.html#pcx_api
# for the documentation describing the format of the code contained in this file
#
package require pcx
pcx::register base64
pcx::tcldep 2.3.2 needs tcl 8.2
namespace eval ::base64 {}
# Using the indirections below looks to be quite pointless, given that
# they simply substitute the commands for others. I am doing this for
# two reasons.
# First, the rules coming after become self-commenting, i.e. a
# maintainer can immediately see what an argument is supposed to be,
# instead of having to search elsewhere (like the documentation and
# implementation). In this manner our definitions here are a type of
# semantic markup.
# The second reason is that while we have no special checks now we
# cannot be sure if such will (have to) be added in the future. With
# all checking routed through our definitions we now already have the
# basic infrastructure (i.e. hooks) in place in which we can easily
# add any new checks by simply redefining the relevant command, and
# all the rules update on their own. Mostly. This should cover 90% of
# the cases. Sometimes new checks will require to create deeper
# distinctions between different calls of the same thing. For such we
# may have to update the rules as well, to provide the necessary
# information to the checker.
interp alias {} base64::checkLineLength {} checkInt ; #
interp alias {} base64::checkWrapChar {} checkWord ; #
interp alias {} base64::checkData {} checkWord ; #
#pcx::message FOO {... text ...} type
#pcx::scan <VERSION> <NAME> <RULE>
pcx::check 2.3.2 std ::base64::decode \
{checkSimpleArgs 1 1 {
base64::checkData
}}
# NOTE: Is '-maxlen' < 0 allowed?
# Doc doesn't forbid it, code doesn't catch it.
# May crash it however, i.e be a bug.
# Check testsuite.
pcx::check 2.3.2 std ::base64::encode \
{checkSimpleArgs 1 -1 {
{checkSwitches 1 {
{-maxlen base64::checkLineLength}
{-wrapchar base64::checkWrapChar}
} {checkSimpleArgs 1 1 {
base64::checkData
}}}
}}
# Initialization via pcx::init.
# Use a ::base64::init procedure for non-standard initialization.
pcx::complete
|
