aboutsummaryrefslogtreecommitdiff
path: root/src/PJ_pipeline.c
diff options
context:
space:
mode:
authorThomas Knudsen <busstoptaktik@users.noreply.github.com>2017-12-17 18:04:13 +0100
committerGitHub <noreply@github.com>2017-12-17 18:04:13 +0100
commit74ae4b09bbc80edb44a123a8272014d15b7d4b8d (patch)
tree066537112cdc8624136049fade9d61d0ca9ad8b8 /src/PJ_pipeline.c
parent533207012bfd2c5de652b9df8b2104cad82b6988 (diff)
downloadPROJ-74ae4b09bbc80edb44a123a8272014d15b7d4b8d.tar.gz
PROJ-74ae4b09bbc80edb44a123a8272014d15b7d4b8d.zip
Free format everywhere (#693)
* Free format now in cmd lines, in gie, and in init files * Corrected handling of defaults * Add demo of integrated definition and validation * Repair stack-smashing memmove in get_init * repair paralist corruption, clean up debug output * Install test files for nmake builds * Add many improvements following suggestions by @schwehr * Be consistent in requiring lower case everywhere in gie.c Also, this Fixes #703 and Fixes #697
Diffstat (limited to 'src/PJ_pipeline.c')
-rw-r--r--src/PJ_pipeline.c9
1 files changed, 3 insertions, 6 deletions
diff --git a/src/PJ_pipeline.c b/src/PJ_pipeline.c
index c8ce8582..a0ef7c1e 100644
--- a/src/PJ_pipeline.c
+++ b/src/PJ_pipeline.c
@@ -51,12 +51,9 @@
pj_init code, implementing support for multilevel, embedded pipelines.
Syntactically, the pipeline system introduces the "+step" keyword (which
- indicates the start of each transformation step), the "+omit_fwd" and
- "+omit_inv" keywords (which indicate that a given transformation step
- should be omitted when the pipeline is executed in forward, resp. inverse
- direction), and reintroduces the +inv keyword (indicating that a given
- transformation step should run in reverse, i.e. forward, when the pipeline
- is executed in inverse direction, and vice versa).
+ indicates the start of each transformation step), and reintroduces the +inv
+ keyword (indicating that a given transformation step should run in reverse, i.e.
+ forward, when the pipeline is executed in inverse direction, and vice versa).
Hence, the first transformation example above, can be implemented as: