On Feb 6, 4:26 am, Uri Schor <urisc...@[EMAIL PROTECTED]
> wrote:
> Done. I agree that it's a good idea to have all the PIP discussions
> there for the sake of easy search 5 years from now, but perhaps at
> this stage, when people aren't monitoring the SF forums, yet, it'll be
> nice to paste the replies in this Usenet group as well; after all,
> it's not like this group is overloading the Internet backbone...
[KSB] Copy of reply from Source Forge (http://sourceforge.net/forum/
forum.php?thread_id=1931669&forum_id=63825)
Good to hear from you, Uri. Thanks for the kind words & interest in
PIP.
1. The source code for PIP is in the *rtns directories as well as in
code templates in global variables. The definitive code is itself in
PSL, which is compiled into M, and the PSL compiler is itself written
in PSL.
2. PIP do***entation still needs to be separated from Profile
do***entation. This separation was not needed when PIP was simply part
of Profile. For now, your best bet may be to use SQL to create tables,
as well as some PSL queries and updates to those tables. Then look for
new generated code modules and changes to global variables (which is
captured in the GT.M journal files). This should tell you where to
write code to hook up existing M globals. Another possibility is to
start the interactive mode: /opt/pip_V01/dm and execute Do ^DRV. Login
as user 1 password xxx and poke around the menus. Caveat: this part of
PIP will probably change, so don't rely on it for anything more than
to develop your understanding of PIP.
3. The compiler is in the *rtns subdirectories.
4. There are PSL to M and SQL to M compilers. There is no tool to
generate PSL from M. Such a tool would be nice to have, of course!
5. PIP itself is brand new, and no one is using PIP as stand alone
software in production. But we do have customers using Profile on
Oracle. (Of course, as you know, the majority of our customers use
Profile on GT.M.)
Regards
-- Bhaskar
|
