profile n.
1. A control file for a program, esp. a text file
automatically read from each user's home directory and intended
to be easily modified by the user in order to customize the
program's behavior. Used to avoid hardcoded choices (see also dot file, rc
file). 2. [techspeak] A report on the amounts of time
spent in each routine of a program, used to find and tune away the hot
spots in it. This sense is often verbed. Some profiling
modes report units other than time (such as call counts) and/or
report at granularities other than per-routine, but the idea is
similar. 3.[techspeak] A subset of a standard used for a
particular purpose. This sense confuses hackers who wander into
the weird world of ISO standards no end!
Node:progasm, Next:proggy, Previous:profile, Up:= P
=
progasm /proh'gaz-m/ n.
[University of Wisconsin] The euphoria experienced upon the
completion of a program or other computer-related project.
Node:proggy, Next:proglet, Previous:progasm, Up:= P
=
proggy n.
1. Any computer program that is considered a full application.
2. Any computer program that is made up of or otherwise contains
proglets. 3. Any computer program
that is large enough to be normally distributed as an RPM or
tarball.
Node:proglet, Next:program, Previous:proggy, Up:= P
=
proglet /prog'let/ n.
[UK] A short _extempore_ program written to meet an
immediate, transient need. Often written in BASIC, rarely more
than a dozen lines long, and containing no subroutines. The
largest amount of code that can be written off the top of one's
head, that does not need any editing, and that runs correctly the
first time (this amount varies significantly according to one's
skill and the language one is using). Compare toy program, noddy, one-liner
wars.