one little problem ..
At the moment, flx_tangle will take a file x.fdoc and extract the @felix code
to make a file x.flx and the @expect code to make x.expect. Now you can
run flx on x.flx with expect file x.expect.
But you could also run flx on x.fdoc! The only caveat is that after some blank
lines we have an @command. If we have some other text at the top, it will
be treated as documentation by flx_tangle and the webserver, but it will
be treated as Felix code by the compiler.
So now if we get rid of fdoc, then the file x.flx would contain the document.
But now flx_tangle will extract the Felix code .. to x.flx and clobber the file.
Now, my idea for a file named x is that
@felix --> means @tangle x.flx
@expect -> means @tangle x.expect
in other words, there are two "default" tanglers defined, and @felix
and @expect are just shorthands for tangling to these two tanglers.
As you can see the problem is you cannot tangle @felix to x.flx
if the @felix is contained in x.flx in the first place!!
Of course .. we don't need to, since we can execute x.flx directly.
However we might well want to generated a "clean" x.flx file without
the @cruft in it (we can .. but only in another directory).
Hmm ....
--
john skaller
skal...@users.sourceforge.net
http://felix-lang.org
------------------------------------------------------------------------------
CenturyLink Cloud: The Leader in Enterprise Cloud Services.
Learn Why More Businesses Are Choosing CenturyLink Cloud For
Critical Workloads, Development Environments & Everything In Between.
Get a Quote or Start a Free Trial Today.
http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk
_______________________________________________
Felix-language mailing list
Felix-language@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/felix-language
