Yugh, this one is still going : ( (in 0.42.5 and 0.43)
It's basically impossible to use declare/import because of this – it's
actually worse than Roman explained, because the [declare] spam goes
in not just the direct parent but in /every/ parent, getting worse and
worse until the top patch has
Oops... I'd better fix that one.
I'm still not sure how to deal with declares inside abstractions, on
the other hand.
cheers
Miller
On Mon, Feb 02, 2009 at 05:39:34PM -0800, Luke Iannini wrote:
Yo, I've been meaning to mention forever that there's a similar issue
with datastructures. Save a
hi everyone
i once posted a bug to the tracker and it still appears to be there in
version 0.42.3.
since this bug is kind of viral, so that it corrupts patches invisibly
and without being noticed by the author, and also since quite some of my
own patches got affected by that bug, i would like to
Yo, I've been meaning to mention forever that there's a similar issue
with datastructures. Save a datastructure-using patch as an
abstraction, instantiate it in a parent patch, save the parent, and
you'll see template definitions from the child abstraction in the
parent. I'll make another bug
