On Mon, 2004-09-06 at 01:44, chris.danx wrote:

> > But how does it know it? How to specify that in a different way than
> > for make?
> 
> Isn't that information encoded in the source files already?  The tool 
> extracts this information and uses it in the build process.


Not quite -- the build rules have to be encoded, yes.
However the encoding is as executable code, so whilst
technically you're right it is extracted and 'used'
by the build process, from the client's viewpoint
it is simply executed.

The build tool itself is a small Python script
which calls functions from a Python library,
and the user can enhance the processing in Python
embedded in the source being read --
so the integration is fairly seamless.

Contrast to autoconf, make, cake, imake ... :)
In theory, these tools are also well integrated
by the Unix OS and shell -- but I find Python
script better (Perl would no doubt be good too).

-- 
John Skaller, mailto:skaller@users.sf.net
voice: 061-2-9660-0850, 
snail: PO BOX 401 Glebe NSW 2037 Australia
Checkout the Felix programming language http://felix.sf.net



-------------------
To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr
Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/
Beginner's list: http://groups.yahoo.com/group/ocaml_beginners