Reply-To: erik.wachtmeester@bighole.iaf.nl
Denis Braussen wrote in a message to Jean Menten:
JM> I'm trying to get acquainted with the clipper add-on library
JM> CLIP4WIN. I'v got some questions about this library:
 DB> nice idea, excellent choice. :-))
 DB> Clip4win is a (very good) library wich allow you to write REAL 
 DB> WINDOWS EXE (but only in 16 bits, because Clipper makes 16 
 DB> bits *.obj) The structure of your PRG is, in such a windows 
 DB> style programming, very close from C style. (BUT, last Version 
 DB> of Clip4Win include an OOP engine which allow you to create 
 DB> your own classes...)
Hmm. I'm quite new to Windows programming, but wouldn't it be easier/better 
o
write a user interface in e.g. Delphi, C++ Builder or Visual C++ that
communicates with a Clipper engine on the background through named pipes or
shared memory? I don't know if a Clipper library that supports named pipes or
shared memory exists, but if yes, you've got a much more flexible solution. 
The
front end could also been written for OS/2, X11, System7, Java, etc., and the
Clipper engine could be running on another machine (maybe even supporting
different clients). The latter would only work with named pipes of course,
because shared memory over different machines just isn't possible...
Regards,
Erik 
---
---------------