"Leslie P. Polzer" <sky-A/[email protected]>
writes:
> What do the hunks for src/views/view/utils.lisp do then, if they don't
> fix the problem (although it says "fix disappearing view fields")?
>
> Is this some precursor for the full fix, or maybe an only slightly
> related fix?
Precursor in the sense that they fix the problem (disappearing fields)
that was masking the real problem (not possible to override an inherited
inline with a proper-mixin, as the demo tries to do).
>> The reason the new test does as it does is that proper mixin data in
>> indirect mixins is deleted too early. I think this can be
>> straightforwardly solved with an enhancement to
>> map-expanding-mixin-fields, streaming its results directly to
>> factor-overridden-fields, and having the latter sort elements as they
>> arrive. It would even make GOVF a little faster and memory-lighter,
>> theoretically. I just thought of it 5min ago, so we'll see.
>
> Very good. This is one of the things that keeps us from releasing
> 0.8.3.
Okay, here are three field topologies (mixins have branches to right to
their fields, vertical link means part of same `view' object, NATO PA as
field name symbols). Which sierra should win in each?
CASE 1:
echo-----november
| |
| sierra₁
|
victor---sierra₂
CASE 2:
echo-----alpha---november
| |
| sierra₁
|
victor---sierra₂
CASE 3:
echo-----sierra₁
|
victor---alpha---november
|
sierra₂
This is the generalization of the true-inlines uniqueness problem. Note
that in
echo
|
sierra₁
|
sierra₂
sierra₂ will always win, regardless of whether sierra₁ is inline or
proper-mixin. This is ideal when taking into account inheritance; more
special view-fields are always later.
The other alternative is to allow all sierras to be included, which is
slot-name-clash-control. But should that go before 0.8.3?
--
Sorry but you say Nibiru is a Hoax? Doesnt Exist? So maybe The
Sumerian people doesnt exist also! --Anonymous by way of SkI
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"weblocks" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/weblocks?hl=en
-~----------~----~----~----~------~----~------~--~---
