[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Tree structure
In article <1994Jan19.073249.19777@sophia.inria.fr>, rlin@apple.fcit.monash.edu.au (Richard Lin Kuang-Hsu) writes:
|> Dear Sir,
|>
|> Our Centaur has been runnung OK so far. But there are some
|> message wont show when we done something wrong. Therefore, I
|> have to ask for help.
|>
|> Question 1: Can I change the tree structure of my own language(Z),
|> or I have to follow the tree structure like Exp?
We advise you to maintain the basic structure of the language
hierarchy, especially since Centaur1.3 will offer a command to create
the hierarchy interactively, in just a few seconds, with resources
created automatically. However, if you are using only metal or only
sdf, you might change L/syntax/metal -> L/syntax, for example.
|> I try to update the
|> directory structure with less levels. I do change all the .rdb files
|> correspond to the new directory structure. Then I cannot read the
|> test files(e.g, test.Z).
In any case, the language hierarchy structure has no effect on
Centaur. This is certainly a resource problem.Check for the following:
1) In the .centaur.rdb, write Centaur.Z*Root:user and
remove all other Root resources from other files.
2) Check for spelling errors.
3) Check that no resource split onto two lines has a blank space
after the backslash (i.e., is must be backslash then newline only).
|> The following is the rdb files:
|> ------ .centaur.rdb ----
|>
|> Centaur.UserFormalisms: (Z)
|> Centaur.Z.Database.UserDefaults: \
|> centaur/Z/Z.rdb
|> ----- Z.rdb ------------
|>
|> Centaur.Z.Root: user
|> Centaur.Z.Location: centaur/Z/metal
|> Centaur.Z.Mode: std
|>
|> Centaur.METAL.Env: module
|> Centaur.METAL.env.Root: app
^^^ bizarre
|> Centaur.METAL.env.Location: centaur/tables/metal/environment
centaur/Z/environment instead perhaps.
|> Centaur.METAL.env.Mode: interp
|>
|> Centaur.Z.SyntaxManager.Syntax.Root: user
|> Centaur.Z.SyntaxManager.Syntax.Location: centaur/Z/metal
|> Centaur.Z.SyntaxManager.Syntax.Mode: std
|> Centaur.Z.ppml.Database.UserDefaults: centaur/Z/pprinters.rdb
...
|> ----- pprinters.rdb -----
|>
|> Centaur.Z.ppml.std.Database.UserDefaults: \
|> centaur/Z/std/std.rdb
...
|> Centaur.Z.ppml.std.Root: user
|> Centaur.Z.ppml.std.Location: centaur/Z/std
|> Centaur.Z.ppml.std.Mode: compiled
The other resources shouldn't have any influence on finding files.
|>
|> Question 2:
|> Is Metal capabile of handling 'user defined data type (e.g., struct
|> in C)'
Yes. You may write:
implemented as MYCLASS;
in your Metal program as long as you have defined the vtp class
"myclass" and a creation function for this class. If you would
like an example of this (or a solution), please contact me for
assistance in defining a new vtp class. Unfortunately, the new vtp
document, which explains this well, has not been distributed yet.
It arrives with centaur1.3 in a couple of weeks.
|> and 'user defined operator and relationship'?
I don't understand this.
Ian
- References:
- Tree structure
- From: rlin@apple.fcit.monash.edu.au (Richard Lin Kuang-Hsu)