W3C home > Mailing lists > Public > public-qt-comments@w3.org > April 2016

[Bug 29574] Default visibility of accepted components

From: <bugzilla@jessica.w3.org>
Date: Wed, 20 Apr 2016 06:34:41 +0000
To: public-qt-comments@w3.org
Message-ID: <bug-29574-523-6Fa6nK4hGK@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=29574

Abel Braaksma <abel.braaksma@xs4all.nl> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |abel.braaksma@xs4all.nl

--- Comment #3 from Abel Braaksma <abel.braaksma@xs4all.nl> ---
I think I agree with Max here. In the analogy with classes, if a class uses a
library, then when someone uses that class, it would automatically import and
open the used libraries. Existing languages don't work this way.

If you have package A, B, C, and package X uses A, B and C. Then you distribute
package X and someone uses your package, then all from A, B and C will
immediately be exposed as well, even though they are in entirely different
packages.

This seems counter-intuitive: a user writes <xsl:use-package name="X"> and he
gets everything from packages with names A, B and C as well, without writing a
use-package statement for it. That's a surprising side-effect.

Yes, we have a workaround to flip the default. And yes, I believe this was
discussed before as well and there are pros and cons to both sides, but I lean
towards flipping the default. I don't see much harm in doing so, in fact, I
think it is a good improvement.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Wednesday, 20 April 2016 06:34:45 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:57:59 UTC