On Wednesday, 30 January 2013 at 20:22:11 UTC, Jacob Carlborg
wrote:
If you have a public and a private function in the same module,
it's possible to implement the two functions in two separate
object files. The private function must then be available in
the object file to link the program
On Wednesday, 30 January 2013 at 20:22:11 UTC, Jacob Carlborg
wrote:
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
On 2013-01-31 11:11, Dicebot wrote:
Ugh, how can you split module into two source/object files? Naive
approach will result in linker error due to multiple definition of
ModuleInfo. I did not know it was possible, would have been really cool
to have.
I'm not 100% sure if it's possible, but
On Monday, January 28, 2013 18:05:37 Dicebot wrote:
http://wiki.dlang.org/DIP22
There are two important issues with current protection attribute
design:
* Senseless name clashes between private and public symbols
* No way to specify internal linkage storage class
This DIP addresses
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?
On Wednesday, 30 January 2013 at 09:29:17 UTC, Dicebot wrote:
Case 1 (binary level, C + D):
- sample.d -
module sample;
private int func() { return 42; }
--
- oops.c -
#include stdio.h
extern int _D6sample4funcFZi();
void* _Dmodule_ref = 0;
void*
On Wednesday, 30 January 2013 at 10:45:26 UTC, Jacob Carlborg
wrote:
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
I have continued with the translation of the book. At this point there
are 551 pages in English of total 711 pages in Turkish.
In addition to many corrections and additions throughout the book, there
are the following chapters translated:
* Universal Function Call Syntax (UFCS)
* Properties
