Yes, that is a part of REBOL flexibility, you can use anything you like.
The ability to build our own tools in a pretty small timeframe is one of REBOL's main features.
However, regarding the toolchain - I seriously recommend all users to try INCLUDE, otherwise they don't even know what they are missing.
and I agree with this.
I know for a fact how hard you worked for it to be non-intrusive to other toolchains.
(many users have reimplemented their own version, but my version has probably the longest PITL usage, development and testing "tradition")
...and also it incorporates many ideas/advices from many sources, not just my own ideas
INCLUDE taught me that it really makes sense to maintain backward compatibility between R3 and R2, which is what BrianH is doing when backporting some R3 functions to R2.
Also, the INCLUDE is striving (successfully IMO) to "bridge the gap" between R3 and R2 by providing the same functionality in the same piece of code. Also, I bet it is much easier to have it written in the "forward/backward" compatible manner than to need to maintain two different scripts.
Ladislav: can INCLUDE now be used to run the same code both from sources and encapped, with no code change?
I am not completely sure what your question is, but we use it to:
1) run the code from the source 2) encap the above code as well, both at the same time
When I click on any file icon here, I usually use INCLUDE to run the code, in fact
(and preprocess it at the same time, if needed)
I just mean enabling any REBOL app to run unchanged from sources (using DO) or encapped.
what is "encapped"? once encapped, it is just an .exe here
but, certainly, I use INCLUDE to run (e.g. when testing) any REBOL application otherwise needing preprocessing, i.e. such that even could not be run by DO; of course, such applications that can be run by DO can be run by INCLUDE as well
Encapped: executable binary generated by /Encap.
Why would you want INCLUDE to run such application?
Ok, let's try another way. :-) For a given REBOL app codebase that can be run with DO, can INCLUDE be used in such codebase to enable application preprocessing suitable for /Encap while letting it still be run using a simple DO?
INCLUDE can be used wherever DO can be used. I guess that answers your question.