[developers] Bug in interactive unification

[Woodley Packard]

My best guess is LUI expected a #D structure instead of a symbol; e.g.

 #D[zero]

One could argue that LUI should be a bit more forgiving in enforcing type constraints on its commands.  Both internally and in the protocol, atomic values are treated differently from feature structures.  An atomic value at the top level is unanticipated, but I think it should work just fine if wrapped into a (trivial) feature structure.

Woodley

>> On Nov 11, 2020, at 9:42 AM, Guy Emerson <gete2 at cam.ac.uk> wrote:
> 
> Hi Stephan,
> 
> The command is:
> 
> process_complete_command(): `avm 1 ZERO "zero - expanded"
>  '
> 
> YZLUI: Received unknown lkb-protocol top-level command: AVM
> 
> Best,
> Guy
> 
>> Am Mi., 11. Nov. 2020 um 16:57 Uhr schrieb Stephan Oepen <oe at ifi.uio.no>:
>> hi guy,
>> 
>> > I also get this behaviour (no LUI window appearing) if I try to display a type that has no features (obviously, this isn't a useful display on its own, but it would be helpful for interactive unification to be able to drag and drop the type).  The log file says:
>> >
>> > YZLUI: Received unknown lkb-protocol top-level command: AVM
>> 
>> could you send the complete log output, i.e. including the 'avm'
>> command that LUI fails to recognize?
>> 
>> oe
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.delph-in.net/archives/developers/attachments/20201111/5a866606/attachment.html>