Hi Rowan, wt., 30 lip 2019 o 10:48 Rowan Collins <rowan.coll...@gmail.com> napisał(a):
> I think there's some confusion here, because establishing the concept of a > package as separate from a namespace is exactly what I proposed. > > Here's a previous message (technically in the same thread, but from 18 > months ago) where I also mentioned class visibility: > https://externals.io/message/101323#101390 > Was thinking about similar, a package with own identity and a way to declare autoload and other stuff. Was even thinking it could use a double colon which I've proposed way back in the same thread and with a delimiter in name all related symbols could be stored in package individual symbol tables, it won't collide with namespaced and global ones and would be easier to detect if tried to use an internal symbol in another context like other package or in global code. It could introduce a few more keywords like: * "package" - for declaring package name and declares, * "export" - for explicit declare of publicly available symbols which then could be detectable etc. for visibility features, * "expect" - for explicit declare of required dependencies Last two are for future features and the first one could be enough for shaping how it could look like. For eg. some of my thoughts https://gist.github.com/brzuchal/c45010f0dd20642b470eeee8b9c56c5f I know it's out of the main topic but IMO we should start another one and I'm pretty sure I've mentioned that earlier. If we wanna shape package for PHP then the separate discussion could be a good idea. -- regards / pozdrawiam, -- Michał Brzuchalski about.me/brzuchal brzuchalski.com
