Re: import with renaming and public import inside module

2014-04-29 Thread ketmar via Digitalmars-d-learn
On Monday, 28 April 2014 at 15:57:16 UTC, anonymous wrote: `zmod.symbol` works, too. no, it's not. at least on latest GDC. I don't think so. The point of the renamed import is that you have to use the new name. but i renamed only my.module, not others. nothing hints me that renaming is SO

Re: import with renaming and public import inside module

2014-04-29 Thread bearophile via Digitalmars-d-learn
ketmar: so it's broken beyond any repair. so sad. The current implementation of the module system has some problems, that are being worked on. If you think some part of the module system design is not good enough, then try to ask for an enhancement :-) No need to be sad. Bye, bearophile

Re: import with renaming and public import inside module

2014-04-29 Thread Artur Skawina via Digitalmars-d-learn
On 04/29/14 11:57, ketmar via Digitalmars-d-learn wrote: On Monday, 28 April 2014 at 15:57:16 UTC, anonymous wrote: `zmod.symbol` works, too. no, it's not. at least on latest GDC. It certainly works here; if it didn't it would be a frontend problem. I don't think so. The point of the renamed

Re: import with renaming and public import inside module

2014-04-29 Thread bearophile via Digitalmars-d-learn
Artur Skawina: The D module system has a lot of problems and certainly needs to be completely redesigned from scratch, I don't think it will be redesigned from scratch (and if that happens I see no proof that the redesign will be better than the original design). So better to fix its major

Re: import with renaming and public import inside module

2014-04-29 Thread anonymous via Digitalmars-d-learn
On Tuesday, 29 April 2014 at 09:57:08 UTC, ketmar wrote: On Monday, 28 April 2014 at 15:57:16 UTC, anonymous wrote: `zmod.symbol` works, too. no, it's not. at least on latest GDC. Works for me with Ubuntu's gdc 4.8.2-1ubuntu6. My little test case: my/module_.d: --- module my.module_;

Re: import with renaming and public import inside module

2014-04-29 Thread ketmar via Digitalmars-d-learn
On Tuesday, 29 April 2014 at 10:57:13 UTC, Artur Skawina via Digitalmars-d-learn wrote: The D module system has a lot of problems and certainly needs to be completely redesigned from scratch i don't see any real flaws in it. it's just little inconsistencies that can be easily fixed.

Re: import with renaming and public import inside module

2014-04-29 Thread ketmar via Digitalmars-d-learn
On Tuesday, 29 April 2014 at 10:44:44 UTC, bearophile wrote: The current implementation of the module system has some problems, that are being worked on. If you think some part of the module system design is not good enough, then try to ask for an enhancement :-) No need to be sad. ah, i can't

Re: import with renaming and public import inside module

2014-04-29 Thread ketmar via Digitalmars-d-learn
On Tuesday, 29 April 2014 at 11:10:06 UTC, anonymous wrote: Works for me with Ubuntu's gdc 4.8.2-1ubuntu6. ah, don't you believe that i *really tested* it before posting, with latest GDC from git (which i builds routinely on dayly basis)? Personally, I think the current behaviour is fine.

Re: import with renaming and public import inside module

2014-04-29 Thread ketmar via Digitalmars-d-learn
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.

Re: import with renaming and public import inside module

2014-04-29 Thread bearophile via Digitalmars-d-learn
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

Re: import with renaming and public import inside module

2014-04-29 Thread anonymous via Digitalmars-d-learn
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

Re: import with renaming and public import inside module

2014-04-29 Thread ketmar via Digitalmars-d-learn
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

Re: import with renaming and public import inside module

2014-04-29 Thread bearophile via Digitalmars-d-learn
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

Re: import with renaming and public import inside module

2014-04-29 Thread ketmar via Digitalmars-d-learn
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

Re: import with renaming and public import inside module

2014-04-29 Thread Mike Parker via Digitalmars-d-learn
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

Re: import with renaming and public import inside module

2014-04-29 Thread ketmar via Digitalmars-d-learn
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

Re: import with renaming and public import inside module

2014-04-29 Thread ketmar via Digitalmars-d-learn
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.

Re: import with renaming and public import inside module

2014-04-29 Thread ketmar via Digitalmars-d-learn
fuck. nobody approves my posts in mailing list. if i want to spam this forum — i can do it here. shit.

Re: import with renaming and public import inside module

2014-04-29 Thread ketmar via Digitalmars-d-learn
On Tuesday, 29 April 2014 at 21:21:10 UTC, ketmar wrote: bye. will never write here again.

Re: import with renaming and public import inside module

2014-04-28 Thread anonymous via Digitalmars-d-learn
On Monday, 28 April 2014 at 00:52:50 UTC, ketmar wrote: module my.module; public import other.module; … module mainprogram; import my.module; now i can access other.module symbols without qualifiers and another case: module mainprogram; import zmod = my.module; now i CAN'T access

import with renaming and public import inside module

2014-04-27 Thread ketmar via Digitalmars-d-learn
i wrote a module which public imports other modules (to avoid importing 'em by hand, 'cause import lists depends on version()). then i imported this 'main' module with renaming: import zmod = my.module; now i can't acces any identifiers from modules that my.module public imports and i forced