On Sunday, 26 May 2013 at 23:35:43 UTC, mimi wrote:
import std.stdio;
struct S
{
int bigUglyName;
void foo( S s )
{
alias bigUglyName local;
alias s.bigUglyName b;
writeln( "bigUglyName (AKA local)=", local, " b=", b );
}
}
void main()
{
S s1;
S
On Sunday, 26 May 2013 at 23:37:01 UTC, mimi wrote:
Wow! thanks!
"offsetof" will automatically distribute over the arguments so to
get the offsets of a tuple you can just do:
auto tmp = TP.offsetof;
And "tmp" will be a tuple of the offsets.
import std.stdio;
struct S
{
int bigUglyName;
void foo( S s )
{
alias bigUglyName local;
alias s.bigUglyName b;
writeln( "bigUglyName (AKA local)=", local, " b=", b );
}
}
void main()
{
S s1;
S s2;
s1.bigUglyName = 1;
s2.bigUglyName = 2;
Wow! thanks!
On Sun, 26 May 2013 17:59:32 +0200, Ali Çehreli wrote:
On 05/26/2013 05:38 AM, Simen Kjaeraas wrote:
> Tuple!(size_t, size_t)[][] data = createData();
> immutable dataImm = assumeUnique(data);
> data = null; // Simply to ensure no mutable references exist.
The last line is
On 05/26/2013 06:50 PM, Ellery Newcomer wrote:
On Sunday, 26 May 2013 at 16:28:33 UTC, Mike Wey wrote:
Try prefixing the python lib with -L like so:
dmd -unittest -property -debug -gc -version=Python_2_7_Or_Later
-version=Python_2_6_Or_Later -version=Python_2_5_Or_Later
-version=Python_2_4_Or_
On Sunday, 26 May 2013 at 16:28:33 UTC, Mike Wey wrote:
Try prefixing the python lib with -L like so:
dmd -unittest -property -debug -gc
-version=Python_2_7_Or_Later -version=Python_2_6_Or_Later
-version=Python_2_5_Or_Later -version=Python_2_4_Or_Later
-L-ldl -L/usr/lib/python2.7/config/lib
On 05/26/2013 05:18 PM, Ellery Newcomer wrote:
On 05/26/2013 08:10 AM, Ellery Newcomer wrote:
On 05/26/2013 07:55 AM, Jesse Phillips wrote:
On Sunday, 26 May 2013 at 05:01:10 UTC, Ellery Newcomer wrote:
I have a project here which fails on link on ubuntu 12.10.
It give undefined reference err
On 05/26/2013 05:38 AM, Simen Kjaeraas wrote:
> Tuple!(size_t, size_t)[][] data = createData();
> immutable dataImm = assumeUnique(data);
> data = null; // Simply to ensure no mutable references exist.
The last line is not needed. assumeUnique already does that. :)
Ali
On Sunday, 26 May 2013 at 14:19:13 UTC, mimi wrote:
Hi!
I am want to get list of fields types and offsets in struct by
the template.
I.e., lookup through this struct:
struct S {
int a;
string b;
someptr* c;
};
template Lookup!( S )(); returns something as:
field #0, int, offset 0
field #1,
On 05/26/2013 08:10 AM, Ellery Newcomer wrote:
On 05/26/2013 07:55 AM, Jesse Phillips wrote:
On Sunday, 26 May 2013 at 05:01:10 UTC, Ellery Newcomer wrote:
I have a project here which fails on link on ubuntu 12.10.
It give undefined reference errors for functions in libdl and libutil.
For some
On 05/26/2013 07:55 AM, Jesse Phillips wrote:
On Sunday, 26 May 2013 at 05:01:10 UTC, Ellery Newcomer wrote:
I have a project here which fails on link on ubuntu 12.10.
It give undefined reference errors for functions in libdl and libutil.
For some reason, ld won't cooperate unless you pass -ldl
On Sunday, 26 May 2013 at 14:19:13 UTC, mimi wrote:
Hi!
I am want to get list of fields types and offsets in struct by
the template.
I.e., lookup through this struct:
struct S {
int a;
string b;
someptr* c;
};
template Lookup!( S )(); returns something as:
field #0, int, offset 0
field #1,
On Sunday, 26 May 2013 at 05:01:10 UTC, Ellery Newcomer wrote:
I have a project here which fails on link on ubuntu 12.10.
It give undefined reference errors for functions in libdl and
libutil. For some reason, ld won't cooperate unless you pass
-ldl -lutil at the end of the command string. Hol
Hi!
I am want to get list of fields types and offsets in struct by
the template.
I.e., lookup through this struct:
struct S {
int a;
string b;
someptr* c;
};
template Lookup!( S )(); returns something as:
field #0, int, offset 0
field #1, string, offset 8,
field #2, someptr, offset 16
How
On Sunday, 26 May 2013 at 12:08:41 UTC, Joseph Rushton Wakeling
wrote:
On 05/24/2013 05:59 PM, Ali Çehreli wrote:
The following simple example uses mutable data but it should
work with 'const' too.
Limiting ourselves to read-only, won't there still be a
slowdown caused by
multiple threads try
On Sun, 26 May 2013 14:06:39 +0200, Joseph Rushton Wakeling
wrote:
On 05/24/2013 04:39 PM, Simen Kjaeraas wrote:
First, *is* it read-only? If so, store it as immutable and enjoy free
sharing. If not, how and why not?
I can confess that it's as simple as feeling extremely uncomfortable
deal
On Sun, 26 May 2013 14:06:39 +0200, Joseph Rushton Wakeling
wrote:
On 05/24/2013 04:39 PM, Simen Kjaeraas wrote:
First, *is* it read-only? If so, store it as immutable and enjoy free
sharing. If not, how and why not?
I can confess that it's as simple as feeling extremely uncomfortable
de
On 05/24/2013 05:59 PM, Ali Çehreli wrote:
> The following simple example uses mutable data but it should work with
> 'const' too.
Limiting ourselves to read-only, won't there still be a slowdown caused by
multiple threads trying to access the same data? The particular case I have
will involve c
On 05/24/2013 04:39 PM, Simen Kjaeraas wrote:
> First, *is* it read-only? If so, store it as immutable and enjoy free
> sharing. If not, how and why not?
I can confess that it's as simple as feeling extremely uncomfortable dealing
with immutable where it relates to any kind of complex data structu
huh. I haven't run into it on fedora. python is built
differently, though.
dmd -L-lpthread -L-ldl -L-lutil -L-L/usr/lib -L-lz
/usr/lib/python2.7/config/libpython2.7.a -debug
-ofbuild/lib.linux-x86_64-2.7/link {lotsaobjectfiles} -L-ldl
-L-lutil -v
Well, that should work fine, although the
21 matches
Mail list logo
