On 2011-04-21 03:37, Eric Poggel (JoeCoder) wrote:
On 4/20/2011 7:07 PM, Andrew Wiley wrote:
I'm working on a project that looks like it'll need manual memory
management (the end goal is to get it running on ARM using GDC, where
the GC doesn't seem to behave (that goal might be unrealistic, but
On 4/20/2011 7:07 PM, Andrew Wiley wrote:
I'm working on a project that looks like it'll need manual memory
management (the end goal is to get it running on ARM using GDC, where
the GC doesn't seem to behave (that goal might be unrealistic, but I can
hope))
I wonder if it would be useful to hav
On Wed, 20 Apr 2011 19:07:43 -0400, Andrew Wiley
wrote:
I'm working on a project that looks like it'll need manual memory
management
(the end goal is to get it running on ARM using GDC, where the GC doesn't
seem to behave (that goal might be unrealistic, but I can hope)), and I'm
trying to
I'm working on a project that looks like it'll need manual memory management
(the end goal is to get it running on ARM using GDC, where the GC doesn't
seem to behave (that goal might be unrealistic, but I can hope)), and I'm
trying to figure out how to deal with closures. My understanding is that a
For me, Logger needs to be simple but feature complete. Here is my ideal
syntax:
Logger log = new Logger();
log.warn("bewarned");
log.error("error code: %d", 42);
log.fatal("Derp");
Fine if you remove the first line, switching the output is something we
rarely do, so we shouldn't mandate th
On Wed, 20 Apr 2011 19:35:33 +0300, Sean Kelly
wrote:
On Apr 20, 2011, at 9:23 AM, Andrei Alexandrescu wrote:
Generally, I think a good logging library should:
- be small and simple to use
- allow defining arbitrary backends
- allow switching backends dynamically
- offer compile-time co
On Wed, 20 Apr 2011 20:02:58 +0300, dsimcha wrote:
== Quote from Sean Kelly (s...@invisibleduck.org)'s article
And with all the legacy code, the crufty old
approach to doing things will stick around for a Long Time Yet. Still,
if D isn't an option, at least 0x eases some of the pain of using
Sean Kelly wrote:
On Apr 20, 2011, at 10:46 AM, JimBob wrote:
"Sean Kelly" wrote in message
news:mailman.3597.1303316625.4748.digitalmar...@puremagic.com...
On Apr 20, 2011, at 5:06 AM, Don wrote:
Sean Kelly wrote:
On Apr 16, 2011, at 1:02 PM, Robert Jacques wrote:
On Sat, 16 Apr 2011 15:32
On Apr 20, 2011, at 10:46 AM, JimBob wrote:
>
> "Sean Kelly" wrote in message
> news:mailman.3597.1303316625.4748.digitalmar...@puremagic.com...
> On Apr 20, 2011, at 5:06 AM, Don wrote:
>
>> Sean Kelly wrote:
>>> On Apr 16, 2011, at 1:02 PM, Robert Jacques wrote:
On Sat, 16 Apr 2011 15:32
On 20.04.2011 20:09, Robert Clipsham wrote:
Hey folks,
I've just finished porting my web framework from D1/Tango to
D2/Phobos, and in the transition lost logging functionality. As I'll
be writing a logging library anyway, I wondered if there'd be interest
in a std.log? If so, is there a curre
"Sean Kelly" wrote in message
news:mailman.3597.1303316625.4748.digitalmar...@puremagic.com...
On Apr 20, 2011, at 5:06 AM, Don wrote:
> Sean Kelly wrote:
>> On Apr 16, 2011, at 1:02 PM, Robert Jacques wrote:
>>> On Sat, 16 Apr 2011 15:32:12 -0400, Walter Bright
>>> wrote:
The dmd s
On 4/20/2011 9:28 AM, Sean Kelly wrote:
Software testing theory has suggestions for how to reduce the number of test
cases here with only a small sacrifice in general error detection. Still,
the fewer switches the better :-)
Currently I test with all combinations of switches that affect code g
On 4/17/2011 11:44 AM, Caligo wrote:
pfff... I really don't know what to say about C++0x.
A comparison of new C++0x features with D:
http://www.digitalmars.com/d/2.0/cpp0x.html
== Quote from Sean Kelly (s...@invisibleduck.org)'s article
> And with all the legacy code, the crufty old
> approach to doing things will stick around for a Long Time Yet. Still,
> if D isn't an option, at least 0x eases some of the pain of using C++.
Exactly how I feel about C++1x. It adds a l
On 4/20/11 11:35 AM, Sean Kelly wrote:
On Apr 20, 2011, at 9:23 AM, Andrei Alexandrescu wrote:
Generally, I think a good logging library should:
- be small and simple to use
- allow defining arbitrary backends
- allow switching backends dynamically
- offer compile-time control, including ze
On Apr 17, 2011, at 11:44 AM, Caligo wrote:
> pfff... I really don't know what to say about C++0x. Everyday I fall
> more in love with D. To know that I'll have to spend time learning
> all the new things in C++ just depresses me. Sure, there are some
> nice features, but I rather spend that ti
On Apr 20, 2011, at 9:23 AM, Andrei Alexandrescu wrote:
>
> Generally, I think a good logging library should:
>
> - be small and simple to use
>
> - allow defining arbitrary backends
>
> - allow switching backends dynamically
>
> - offer compile-time control, including zero overhead "all loggi
On Wed, 20 Apr 2011 20:09:30 +0400, Robert Clipsham
wrote:
Hey folks,
I've just finished porting my web framework from D1/Tango to D2/Phobos,
and in the transition lost logging functionality. As I'll be writing a
logging library anyway, I wondered if there'd be interest in a std.log?
I
On 4/20/11 6:09 PM, Robert Clipsham wrote:
[…] and another candidate may be http://logging.apache.org/log4j/.
You might want to have a look at SLF4J and Logback, which were written
by the author of log4j as a successor to it.
David
On 2011-04-20 17:32, Steven Schveighoffer wrote:
My biggest pet-peeve with netbeans is when I want to change a value to a
string literal, I highlight what I want to change, then type a quote to
start typing the literal, the freaking thing instead just puts quotes
around the highlighted text (whic
On Apr 19, 2011, at 11:04 PM, Walter Bright wrote:
> On 4/19/2011 7:11 PM, Brad Roberts wrote:
>> The stronger argument, that I agree with, is not having flag based
>> sometimes warnings. The more flags you have, the more complex the matrix
>> of landmines there are. I hate micro-managment, in a
On 4/20/11 11:09 AM, Robert Clipsham wrote:
Hey folks,
I've just finished porting my web framework from D1/Tango to D2/Phobos,
and in the transition lost logging functionality. As I'll be writing a
logging library anyway, I wondered if there'd be interest in a std.log?
If so, is there a current
On Apr 20, 2011, at 5:06 AM, Don wrote:
> Sean Kelly wrote:
>> On Apr 16, 2011, at 1:02 PM, Robert Jacques wrote:
>>> On Sat, 16 Apr 2011 15:32:12 -0400, Walter Bright
>>> wrote:
The dmd startup code (actually the C startup code) does an fninit. I never
thought about new thread
Hey folks,
I've just finished porting my web framework from D1/Tango to D2/Phobos,
and in the transition lost logging functionality. As I'll be writing a
logging library anyway, I wondered if there'd be interest in a std.log?
If so, is there a current logging library we would like it to be bas
On 04/20/2011 07:12 AM, KennyTM~ wrote:
On Apr 20, 11 19:28, Daniel Gibson wrote:
I think the DMD way is conformant with the D2 specification, see
http://digitalmars.com/d/2.0/operatoroverloading.html
"e++ [is rewritten as] (auto t=e, ++e, t)", so x=x++; shouldn't change
the value of x. (Yeah,
On 15/04/2011 21:12, Don wrote:
I noticed a lively discussion in Bugzilla about the GC, with speculation
about the impact of a precise GC on speed.
But it seems to me that a dedicated GC for pure functions has enormous
unexplored potential, and might be relatively easy to implement.
This stuff
On Wed, 20 Apr 2011 10:40:22 -0400, Bruno Medeiros
wrote:
On 04/04/2011 20:19, Aleksandar Ružičić wrote:
On Mon, Apr 4, 2011 at 9:05 PM, Steven Schveighoffer
wrote:
> On Mon, 04 Apr 2011 14:51:02 -0400, Aleksandar Ružičić
>wrote:
>
>> On Mon, Apr 4, 2011 at 8:11 PM, Bruno Medeiros
On 04/04/2011 20:19, Aleksandar Ružičić wrote:
On Mon, Apr 4, 2011 at 9:05 PM, Steven Schveighoffer
wrote:
> On Mon, 04 Apr 2011 14:51:02 -0400, Aleksandar Ružičić
>wrote:
>
>> On Mon, Apr 4, 2011 at 8:11 PM, Bruno Medeiros
>>wrote:
>>>
>>> BTW, I wanna thank for this work (curren
On 13/04/2011 23:39, Adam D. Ruppe wrote:
* Syntax highlighting in the editor :o)
I'm afraid I'll have to say no here... that's a pretty enormous
effort to get working well, and I hate javascript too much to
spend that kind of time with it. Of course, if someone else
has done it, I'm not above a
On 13/04/2011 16:43, Sean Kelly wrote:
Not sure. Is ddbg open and available?
Sent from my iPhone
I was thinking about build tools, but yeah, your point is valid for any
kind of D tool.
--
Bruno Medeiros - Software Engineer
lenochware Wrote:
> Well, I don't understand internal architecture at all, but from user's point
> of
> view it would be good keep some simple and nice way to remove object. I like
> if I
> can have things under control - if I want.
clear(myObjectThatMustGo);
On Wed, 20 Apr 2011 07:37:14 +0300, Kagamin wrote:
D IS TEH typesaving language. Go the D way or go away :3
I think The D Way is to be a debugsaving language before everything
else... ;)
--
Best regards,
Vladimirmailto:vladi...@thecybershadow.net
On Wed, 20 Apr 2011 06:23:01 -0400, bearophile
wrote:
Robert Jacques:
I do GP GPU work, so I use floats all the time. They're also useful for
data storage purposes.
Today GPUs are just starting to manage doubles efficiently (Tesla?).
IIRC, the Fermi Tesla cards do doubles at about 1/2 f
Am 20.04.2011 13:36, schrieb Dmitry Olshansky:
In this case the overall semantics are identical but your expandation
looks like gdc's and mine like dmd's. Therefore I think dmd's is more
correct although less useful.
Generally I think it should just be an error to assign twice in the
same expre
On Apr 20, 11 19:28, Daniel Gibson wrote:
I think the DMD way is conformant with the D2 specification, see
http://digitalmars.com/d/2.0/operatoroverloading.html
"e++ [is rewritten as] (auto t=e, ++e, t)", so x=x++; shouldn't change
the value of x. (Yeah, this is for overloading, but the operator
Sean Kelly wrote:
On Apr 16, 2011, at 1:02 PM, Robert Jacques wrote:
On Sat, 16 Apr 2011 15:32:12 -0400, Walter Bright
wrote:
The dmd startup code (actually the C startup code) does an fninit. I never
thought about new thread starts. So, yeah, druntime should do an fninit on
thread creati
On 20.04.2011 14:16, Mafi wrote:
Am 20.04.2011 12:01, schrieb Dmitry Olshansky:
On 20.04.2011 13:53, Jonathan M Davis wrote:
This was partially discussed before some time ago -
http://www.digitalmars.com/d/archives/digitalmars/D/postincrement_behaviour
_differences_between_dmd_and_gdc_47334
Am 20.04.2011 12:58, schrieb bearophile:
Iain Buclaw:
Skipping all undefined behaviour/which one is correct talk, an alternative
suggestion would be to treat such nonsensical code as an error - like "Cannot
modify the value of a variable twice in the same expression." - as this kind
of thing I
Iain Buclaw:
> Skipping all undefined behaviour/which one is correct talk, an alternative
> suggestion would be to treat such nonsensical code as an error - like "Cannot
> modify the value of a variable twice in the same expression." - as this kind
> of thing I would expect to be almost always a b
Am 20.04.2011 12:01, schrieb Dmitry Olshansky:
On 20.04.2011 13:53, Jonathan M Davis wrote:
This was partially discussed before some time ago -
http://www.digitalmars.com/d/archives/digitalmars/D/postincrement_behaviour
_differences_between_dmd_and_gdc_47334.html
The following statement has d
Robert Jacques:
> I do GP GPU work, so I use floats all the time. They're also useful for
> data storage purposes.
Today GPUs are just starting to manage doubles efficiently (Tesla?).
> For your information, the x87 can only perform computations at 80-bits.
If you compile D1 code that doesn'
Iain Buclaw Wrote:
> suggestion would be to treat such nonsensical code as an error - like "Cannot
> modify the value of a variable twice in the same expression." - as this kind
> of thing I would expect to be almost always a bug.
What about this?
x=(*y)++;
Iain Buclaw Wrote:
> And the backend for GDC interprets it as:
>
> x = x;
> x++;
As I understand, you pass the expression to the backend as is, the backend
interprets it in the C way, and you get surprising result on discrepancy
between C and D semantics?
On 20.04.2011 13:53, Jonathan M Davis wrote:
This was partially discussed before some time ago -
http://www.digitalmars.com/d/archives/digitalmars/D/postincrement_behaviour
_differences_between_dmd_and_gdc_47334.html
The following statement has different behaviours in dmd and gdc.
int x;
x = x
> This was partially discussed before some time ago -
> http://www.digitalmars.com/d/archives/digitalmars/D/postincrement_behaviour
> _differences_between_dmd_and_gdc_47334.html
>
>
> The following statement has different behaviours in dmd and gdc.
>
> int x;
> x = x++;
>
>
> Where the backend
On 04/20/2011 11:33 AM, Iain Buclaw wrote:
This was partially discussed before some time ago -
http://www.digitalmars.com/d/archives/digitalmars/D/postincrement_behaviour_differences_between_dmd_and_gdc_47334.html
The following statement has different behaviours in dmd and gdc.
int x;
x = x++;
This was partially discussed before some time ago -
http://www.digitalmars.com/d/archives/digitalmars/D/postincrement_behaviour_differences_between_dmd_and_gdc_47334.html
The following statement has different behaviours in dmd and gdc.
int x;
x = x++;
Where the backend for DMD interprets it as
== Quote from Andrei Alexandrescu (seewebsiteforem...@erdani.org)'s article
> On 4/19/11 1:04 PM, Timon Gehr wrote:
> > Steven Schveighoffer wrote:
> >> And one other note -- delete will eventually be deprecated. In order to
> >> free memory, you must use clear and GC.free.
> >
> >> -Steve
> >
> >
YES
On 04/20/2011 01:53 AM, dsimcha wrote:
On 4/19/2011 7:30 PM, spir wrote:
And what about requiring "lazy" (and "ref") at the call site; I mean in
the long term? I find this very sensible.
Denis
I wouldn't mind this for "lazy" but would argue heavily against it for "ref".
ref parameters are bot
On 04/20/2011 01:42 AM, Kai Meyer wrote:
On 04/19/2011 05:18 PM, dsimcha wrote:
== Quote from Vladimir Panteleev (vladi...@thecybershadow.net)'s article
To elaborate, I mean allowing code which appears to behave surprisingly
different from the at-a-glance interpretation, unless the programmer k
51 matches
Mail list logo
