Am 30.08.2017 um 10:22 schrieb Marcin Błażejowski:
In foo1 we have empty string str1 but foo2 doesn't contain it.
I'd say it's a bug.
the XML file in wchich bwrite stores the foo1 bundle: there is no
definition of str2 anymore.
You mean str1? Because str2 survives OK for me
? eval foo2
str2 = ~
BTW, there may be an additional small bug. The doc in chapter 14.2 says
about a string declaration: "This can be the keyword null, to produce an
empty string." However, this doesn't work in the bundle context, try this:
string b.check = null # fails
However, perhaps we don't want to have more of this "null" business, and
perhaps it should rather be deprecated for strings, given that empty
strings are already a good way of defining a non-existent string type?