From: Leo F. <leo...@ne...> - 2011-10-12 16:24:03
|
Hi Petra, That's interesting. The XML itself wasn't even parsing (!) I was getting the error "javax.xml.bind.UnmarshalException - with linked exception: [org.xml.sax.SAXParseException: Content is not allowed in prolog.]" within the command exception. That's interesting... I don't know where this is coming from (e.g., don't know about XML parsers); but I do know that ZML without type information does parse no problem (e.g., see examples in parser-zeves/*.zml)..... This error message sounds suspicious to me. Perhaps something wrong in the Jaxb XML generation involving types? Perhaps the fact the typechecker constructs different Type implementations from Corejava? I don't know.... :-( Best, Leo On 12 Oct 2011, at 14:43, Petra Dietrich wrote: > Hi, > > I am trying to typecheck a specification who's parent is given as a zml > file that already contains type annotations. Firstly, is my assumption > that this should work without having to re-typecheck the parent right? > > Here is an example I am experimenting with: > > ─ section test parents toolkit └ > ─ ⊢? ∃x: ℙ(𝔸×𝔸) ⦁ dom x = ∅ └ > > The toolkit parent is derived from standard_toolkit by just translating > it to zml and renaming the Z section. With standard_toolkit as parent, > everything works well, but with toolkit (the zml version of > standard_toolkit) I get the following error: > ERROR "test.utf8", line 1, column 20: Implicit parameters not determined > Expression: dom > ERROR "test.utf8", line 1, column 28: Implicit parameters not determined > Expression: ∅ > > Any ideas what's going on? > > Thanks, > Petra > <toolkit.zml><ATT00001..txt><ATT00002..txt> |