On 2013-01-30 17:26, deadalnix wrote:
The code is in C in the example. But if you replace the C code by
another D module, the exact same reasoning holds.
What point are you trying to make by raising that ? It seems completely
irrelevant to me. Or I didn't inferred the part of the reasoning that
On Tuesday, 29 January 2013 at 16:34:15 UTC, Namespace wrote:
On Tuesday, 29 January 2013 at 15:19:37 UTC, David wrote:
Am 29.01.2013 16:10, schrieb Namespace:
Ahh. That could be a problem: I hate makefiles and never
wrote one.
Hehe,
to quote "ibuclaw":
`make no-sense`
It doesn't need to be
On Wednesday, 30 January 2013 at 12:02:46 UTC, Jacob Carlborg
wrote:
It's not just accessing from C code. Due to D supporting
separate compilation you can have the implementation of a
private method in a separate object file.
The code is in C in the example. But if you replace the C code by
a
On 2013-01-30 10:57, deadalnix wrote:
I understand the risk of breakage. But . . .
Not worth the breakage.
Is this code supposed to work in the first place ? I mean, the private
function is not marked export, the language make no guarantee it will be
accessible from C.
Additionally, does it
On 01/30/2013 10:42 AM, Dicebot wrote:
...
That was the most uneasy part of proposal. I have been thinking for few
hours about it, considering different options. In the end, I have
decided that it is only confusing to one coming from C++ lax approach
and for clean mind it should make perfect sens
On 2013-01-30 00:28, alex wrote:
Okay, I've uploaded a new version that features a basically working
version. There is now a separated mixin insight and expression
evaluation available.
There are still many things left to do though.
I'll give it a try.
--
/Jacob Carlborg
On Wednesday, 30 January 2013 at 09:42:01 UTC, Dicebot wrote:
On Wednesday, 30 January 2013 at 05:29:14 UTC, Jesse Phillips
wrote:
And this results in people writing code that ...? Is there an
example where you can break code in another module by changing
something marked as private?
Examples
On Wednesday, 30 January 2013 at 05:29:14 UTC, Jesse Phillips
wrote:
And this results in people writing code that ...? Is there an
example where you can break code in another module by changing
something marked as private?
Examples separated:
http://forum.dlang.org/post/irrbdrxordjawkryv...@fo
On Wednesday, 30 January 2013 at 03:54:53 UTC, deadalnix wrote:
I have to support that.
static have already quite a lot of different meaning in D, and
adding yet a new one probably not a good idea. Especially when
module level declaration are supposed to be static by default,
so now they can
Case 1 (binary level, C + D):
- sample.d -
module sample;
private int func() { return 42; }
--
- oops.c -
#include
extern int _D6sample4funcFZi();
void* _Dmodule_ref = 0;
void* _D15TypeInfo_Struct6__vtblZ = 0;
void _Dmain() { }
int main()
{
long value = _D6sample
10 matches
Mail list logo
