File: api.inc

package info (click to toggle)
critcl 3.3.1%2Bdfsg-1
  • links: PTS, VCS
  • area: main
  • in suites: forky, sid, trixie
  • size: 9,680 kB
  • sloc: ansic: 41,058; tcl: 12,090; sh: 7,230; pascal: 3,456; asm: 3,058; ada: 1,681; cpp: 1,001; cs: 879; makefile: 333; perl: 104; xml: 95; f90: 10
file content (33 lines) | stat: -rw-r--r-- 1,428 bytes parent folder | download
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

A short note ahead of the documentation: Instead of repeatedly talking
about
"a Tcl script with embbedded C code", or
"a Tcl script containing CriTcl commands",
we call such a script a [vset critcl_script].  A file containing a
[vset critcl_script] usually has the extension [const .tcl] or
[const .critcl].

[comment {
	Uncompleted docs for

	config -I ... - describe the options ...

	Undocumented commands ...

	c++command	-
}]

[subsection {Embedded C Code}]			[include include/api_embedc.inc]
[subsection {Stubs Table Management}]		[include include/api_stubs.inc]
[subsection {Package Meta Data}]		[include include/api_meta.inc]
[subsection {Control & Interface}]		[include include/api_control.inc]
[subsection {Introspection}]			[include include/api_introspection.inc]
[subsection {Build Management}]			[include include/api_bmgmt.inc]
[subsection {Result Cache Management}]		[include include/api_rcache.inc]
[subsection {Build Configuration}]		[include include/api_bconfig.inc]
[subsection {Tool API}]				[include include/api_tools.inc]
[subsection {Advanced: Embedded C Code}]	[include include/api_aembedc.inc]
[subsection {Custom Build Configuration}]	[include include/api_cbconfig.inc]
[subsection {Advanced: Location management}]	[include include/api_location.inc]
[subsection {Advanced: Diversions}]		[include include/api_diversions.inc]
[subsection {Advanced: File Generation}]	[include include/api_generation.inc]