|Newbie questions about Pliant
about defining new operators
|Message posted by jacobfan on 2002/06/15 08:21:09
|To define a new operator,I should use the module
"/pliant/install/ring2.pli",but this module is
only in the scope of "/pliant/language/" and
my own code can't access it at all.I don't want
to use "/pliant/protocol/dns/"'s trick to insert
my own namespace into ring2.pli,which will make
my code not compatible with a standard pliant tree.
Currently I add my own backdoor module "jacob.pli"
into /pliant/language/ which use "/pliant/install/ring2.pli"
as one of its submodules. I don't think this is a
good way to solve the problem.What is a better way
to do this?
|Message posted by jacobfan on 2002/06/15 08:25:18
|Maybe make the "/pliant/install/ring2.pli" publicly accessible?
Since the documentation suggest users to define new operations to
write their programs in a more convenient way.
|Message posted by maybe on 2002/06/15 10:59:58
|Scoped modules are not intended to be linked to directly;
Ring modules (as ring2.pli) are only used to precompile the default
environment in a good order.
To access "operator" (which changes the syntax and hence the parser), you have
to link to "/pliant/language/parser.pli"