April 29, 2014 Re: import with renaming and public import inside module | ||||
---|---|---|---|---|
| ||||
Posted in reply to anonymous | On Tuesday, 29 April 2014 at 11:10:06 UTC, anonymous wrote: specifically, it was derelict sdl bindings. that module itself does public imports, so issue is more complicated. sorry for me being rude. |
April 29, 2014 Re: import with renaming and public import inside module | ||||
---|---|---|---|---|
| ||||
Posted in reply to ketmar | ketmar:
> ah, i can't clearly express myself even in this case, i don't think i can make clear request. it's easier to write code, not words. ;-)
>
> i'm sad not about D or module issues, i'm sad about myself.
One of the most important skills of a programmer (and of course a technical/literary writer) is the ability to express ideas in written text. It's a skill that you develop doing exercise, pushing yourself, finding the sub-parts you are weaker and exercising on them in a focused way, and reading good non-fiction and fiction.
Bye,
bearophile
|
April 29, 2014 Re: import with renaming and public import inside module | ||||
---|---|---|---|---|
| ||||
Posted in reply to ketmar | On Tuesday, 29 April 2014 at 11:23:56 UTC, ketmar wrote: > ah, don't you believe that i *really tested* it before posting, with latest GDC from git (which i builds routinely on dayly basis)? You may have made mistakes when testing, or maybe I have. That's why I provided my testcase. Does it work in your setup? If not, you may want to file a bug with GDC, as it's supposed to work, as far as I can see. > to guard me from name clashes explicitly from the module i imported, not from the others. The other, current behaviour is more defensive. And it's what I'd expect, so I'm fine with it. > perhaps there should be some way to either rename all imports including public from module, or only the module itself, leaving it's public imports intact. if i'll invent nice syntax for it, i'll fill enhancement request with a patch. I don't have a need for that feature. And I don't think there is ample demand. I don't see how `zmod.symbol` or two imports are bad enough to warrant it. But I don't have any kind of authority here, so go for it, if you think it's worthwhile. |
April 29, 2014 Re: import with renaming and public import inside module | ||||
---|---|---|---|---|
| ||||
Posted in reply to bearophile | On Tuesday, 29 April 2014 at 11:28:23 UTC, bearophile wrote:
> One of the most important skills of a programmer (and of course a technical/literary writer) is the ability to express ideas in written text.
the thing is that English neither my native language nor i learned it in school (not really learned it at all in fact). i can express myself in russian, ukrainian and some obscure artificial language, but this will be of little use for the rest of the community. ;-) i can easily read English, but my writing skills are close to nothing.
|
April 29, 2014 Re: import with renaming and public import inside module | ||||
---|---|---|---|---|
| ||||
Posted in reply to ketmar | ketmar:
> the thing is that English neither my native language
Nor mine, as you can see :-) And I am bad with natural languages in general. But you can learn to write "acceptable" English if you do exercises for some years :-)
Bye,
bearophile
|
April 29, 2014 Re: import with renaming and public import inside module | ||||
---|---|---|---|---|
| ||||
Posted in reply to anonymous | On Tuesday, 29 April 2014 at 11:47:07 UTC, anonymous wrote: > You may have made mistakes when testing, or maybe I have. sorry again for being rude. i was really upset and unintentionally made it to you. > That's why I provided my testcase. Does it work in your setup? your sample is ok. but derelict sdl is bad (there are more public imports in it). > The other, current behaviour is more defensive. And it's what I'd expect, so I'm fine with it. that's why i want an option to do it my way. ;-) > I don't have a need for that feature. and i see. this additional feature will not break anything if done properly, but will add a thing for those who need it. |
April 29, 2014 Re: import with renaming and public import inside module | ||||
---|---|---|---|---|
| ||||
Posted in reply to ketmar | On 4/29/2014 8:25 PM, ketmar wrote:
> On Tuesday, 29 April 2014 at 11:10:06 UTC, anonymous wrote:
> specifically, it was derelict sdl bindings. that module itself does
> public imports, so issue is more complicated. sorry for me being rude.
What, exactly, is the problem you are having with public imports in Derelict?
|
April 29, 2014 Re: import with renaming and public import inside module | ||||
---|---|---|---|---|
| ||||
Posted in reply to Mike Parker | On Tuesday, 29 April 2014 at 13:53:58 UTC, Mike Parker wrote:
> What, exactly, is the problem you are having with public imports in Derelict?
it's not derelict issue, sorry is i made you to think that. issue is with the renamed public imports, and dereclit was one that triggered it. nothing bad with derelict, it's really cool by itself. ;-)
|
April 29, 2014 Re: import with renaming and public import inside module | ||||
---|---|---|---|---|
| ||||
Posted in reply to Mike Parker | On Tuesday, 29 April 2014 at 13:53:58 UTC, Mike Parker wrote: ah. besides that i was once unable to build derelict sdl due to undefined symbols like 'ipad' or so, can't really remember. but it's the thing you got when goind bleeding edge, i think. |
Copyright © 1999-2021 by the D Language Foundation