Removing entries from AAs

2011-08-19 Thread useo6
Hi, I've create a little example of my problem: module example; class ExampleClass { public { int mi; this(int i) { mi = i; } } } int main(string[] args) { ExampleClass[hash_t] exp;

Re: Removing entries from AAs

2011-08-19 Thread Timon Gehr
On 08/19/2011 02:01 PM, useo6 wrote: Hi, I've create a little example of my problem: module example; class ExampleClass { public { int mi; this(int i) { mi = i; } } } int main(string[] args) {

Re: Insert array into an AA

2011-08-19 Thread Steven Schveighoffer
On Thu, 18 Aug 2011 06:47:32 -0400, nrgyzer nrgy...@gmail.com wrote: == Auszug aus Robert Clipsham (rob...@octarineparrot.com)'s Artikel On 16/08/2011 20:17, nrgyzer wrote: Hi everyone, I've the following: private static ubyte[][2][hash_t] classInstances; this() {

Re: Removing entries from AAs

2011-08-19 Thread useo6
== Auszug aus Timon Gehr (timon.g...@gmx.ch)'s Artikel On 08/19/2011 02:01 PM, useo6 wrote: Hi, I've create a little example of my problem: module example; class ExampleClass { public { int mi; this(int i) { mi = i;

Re: Empy program running time

2011-08-19 Thread Steven Schveighoffer
On Fri, 19 Aug 2011 01:29:05 -0400, Marco Leise marco.le...@gmx.de wrote: Am 29.07.2011, 17:23 Uhr, schrieb Steven Schveighoffer schvei...@yahoo.com: On Fri, 29 Jul 2011 10:50:52 -0400, bearophile bearophileh...@lycos.com wrote: Steven Schveighoffer: For example, D needs to call all

core.stdc.stdio.stderr != std.stdio.stderr ?

2011-08-19 Thread bearophile
Is this all correct? static import core.stdc.stdio; static import std.stdio; void main() { std.stdio.fprintf(core.stdc.stdio.stderr, Error\n); // OK std.stdio.fprintf(std.stdio.stderr, Error\n); // line 5, error } The latest DMD gives: test.d(5): Error: function core.stdc.stdio.fprintf

Re: core.stdc.stdio.stderr != std.stdio.stderr ?

2011-08-19 Thread Steven Schveighoffer
On Fri, 19 Aug 2011 10:12:11 -0400, bearophile bearophileh...@lycos.com wrote: Is this all correct? static import core.stdc.stdio; static import std.stdio; void main() { std.stdio.fprintf(core.stdc.stdio.stderr, Error\n); // OK std.stdio.fprintf(std.stdio.stderr, Error\n); // line

Re: assertion failure in std.range.iota

2011-08-19 Thread Andrej Mitrovic
http://d.puremagic.com/issues/show_bug.cgi?id=6531

Re: core.stdc.stdio.stderr != std.stdio.stderr ?

2011-08-19 Thread David Nadlinger
On 8/19/11 4:12 PM, bearophile wrote: static import core.stdc.stdio; static import std.stdio; void main() { std.stdio.fprintf(core.stdc.stdio.stderr, Error\n); // OK std.stdio.fprintf(std.stdio.stderr, Error\n); // line 5, error } std.stdio.stderr is a wrapper around

help understanding import libraries

2011-08-19 Thread maarten van damme
I'm really getting confused as to how import libraries actually work. Someone once told me that in order to use an import library one has to write d files declaring the functions so that the dmd compiler knows what's in the lib files. I've never thought any further untill I compiled the gtkd

Re: Insert array into an AA

2011-08-19 Thread nrgyzer
== Auszug aus Steven Schveighoffer (schvei...@yahoo.com)'s Artikel On Thu, 18 Aug 2011 06:47:32 -0400, nrgyzer nrgy...@gmail.com wrote: == Auszug aus Robert Clipsham (rob...@octarineparrot.com)'s Artikel On 16/08/2011 20:17, nrgyzer wrote: Hi everyone, I've the following:

Re: help understanding import libraries

2011-08-19 Thread Jesse Phillips
maarten van damme Wrote: the compiler flags I needed to add was -I for every src directory and -L for the lib file. The problem with that was that those files in the src dir don't declare the functions but also define them. They are the real source code files so I didn't understand why the -L

Re: help understanding import libraries

2011-08-19 Thread Andrej Mitrovic
You don't need the damn -L flag, just pass the .lib file directly and DMD will pass it to the linker.

Re: help understanding import libraries

2011-08-19 Thread Graham Fawcett
On Fri, 19 Aug 2011 12:38:01 -0400, Jesse Phillips wrote: If you wanted (and didn't run out of command line characters) you could list all .d files in every library you are using and have dmd compile everything for you. Then the -L would not be required. Just a reminder, you have dmd @cmdfile

Re: help understanding import libraries

2011-08-19 Thread Graham Fawcett
On Fri, 19 Aug 2011 12:38:01 -0400, Jesse Phillips wrote: If you wanted (and didn't run out of command line characters) you could list all .d files in every library you are using and have dmd compile everything for you. Then the -L would not be required. Just a reminder, you have dmd @cmdfile

Re: help understanding import libraries

2011-08-19 Thread Graham Fawcett
On Fri, 19 Aug 2011 12:38:01 -0400, Jesse Phillips wrote: If you wanted (and didn't run out of command line characters) you could list all .d files in every library you are using and have dmd compile everything for you. Then the -L would not be required. Just a reminder, you have dmd @cmdfile

Re: help understanding import libraries

2011-08-19 Thread Graham Fawcett
On Fri, 19 Aug 2011 12:38:01 -0400, Jesse Phillips wrote: If you wanted (and didn't run out of command line characters) you could list all .d files in every library you are using and have dmd compile everything for you. Then the -L would not be required. Just a reminder, you have dmd @cmdfile

Re: help understanding import libraries

2011-08-19 Thread Graham Fawcett
On Fri, 19 Aug 2011 12:38:01 -0400, Jesse Phillips wrote: If you wanted (and didn't run out of command line characters) you could list all .d files in every library you are using and have dmd compile everything for you. Then the -L would not be required. Just a reminder, you have dmd @cmdfile

Re: help understanding import libraries

2011-08-19 Thread Andrew Wiley
On Fri, Aug 19, 2011 at 9:38 AM, Jesse Phillips jessekphillip...@gmail.comwrote: maarten van damme Wrote: the compiler flags I needed to add was -I for every src directory and -L for the lib file. The problem with that was that those files in the src dir don't declare the functions but

Re: help understanding import libraries

2011-08-19 Thread maarten van damme
and how come the executable I manually linked was 17 times smaller then the other executable? and how does the dll searching works?

Re: duplicates (Re: help understanding import libraries)

2011-08-19 Thread maarten van damme
I saw the same with another user using the web interface, seems like it's buggy 2011/8/19 Graham Fawcett fawc...@uwindsor.ca On Fri, 19 Aug 2011 17:35:00 +, Graham Fawcett wrote: On Fri, 19 Aug 2011 12:38:01 -0400, Jesse Phillips wrote: If you wanted (and didn't run out of command

Re: help understanding import libraries

2011-08-19 Thread Jesse Phillips
Graham Fawcett Wrote: On Fri, 19 Aug 2011 12:38:01 -0400, Jesse Phillips wrote: If you wanted (and didn't run out of command line characters) you could list all .d files in every library you are using and have dmd compile everything for you. Then the -L would not be required. Just a

gdc ldc problems

2011-08-19 Thread maarten van damme
so I have installed ldc,gdc and dmd on my linux box(debian testing) the problem now is that when I try to compiler something using gdc or ldc that imports from core it gives an error (core.* can not be found). the versions of phobos between the 3 are completely out of sync, did I install it the

Re: gdc ldc problems

2011-08-19 Thread Jesse Phillips
On Sat, 20 Aug 2011 03:37:52 +0200, maarten van damme wrote: so I have installed ldc,gdc and dmd on my linux box(debian testing) the problem now is that when I try to compiler something using gdc or ldc that imports from core it gives an error (core.* can not be found). the versions of phobos

Re: gdc ldc problems

2011-08-19 Thread maarten van damme
ooh, thank you :) 2011/8/20 Jesse Phillips jessekphillip...@gmail.com On Sat, 20 Aug 2011 03:37:52 +0200, maarten van damme wrote: so I have installed ldc,gdc and dmd on my linux box(debian testing) the problem now is that when I try to compiler something using gdc or ldc that imports