On 1/11/2013 11:07 PM, master wrote:
On Saturday, 12 January 2013 at 05:20:15 UTC, evilrat wrote:
On Saturday, 12 January 2013 at 04:45:01 UTC, master wrote:
dmd reference coff library problem solved?2.0.61 can use it? How to use?
you need to link with coff? use this tool to convert coff to o
On Saturday, 12 January 2013 at 05:20:15 UTC, evilrat wrote:
On Saturday, 12 January 2013 at 04:45:01 UTC, master wrote:
dmd reference coff library problem solved?2.0.61 can use it?
How to use?
you need to link with coff? use this tool to convert coff to
omf ftp://ftp.digitalmars.com/coffimpl
On 1/11/2013 9:17 PM, David Nadlinger wrote:
Sorry for the rant, [2]
David
No problem. I think it's great that you're the champion for LDC. Having 3 robust
compilers for D is only a win, and I don't think having 3 takes away from D at all.
The 3 compilers have different strengths and weaknes
On Saturday, 12 January 2013 at 04:45:01 UTC, master wrote:
dmd reference coff library problem solved?2.0.61 can use it?
How to use?
you need to link with coff? use this tool to convert coff to omf
ftp://ftp.digitalmars.com/coffimplib.zip
with x64 there is also should be possible to use coff
On Friday, 11 January 2013 at 20:57:57 UTC, Dmitry Olshansky
wrote:
You can print total counts after each bench, there is a TLS
varaible written at the end of it. But anyway I like your
numbers! :)
Okay, I couldn't resist having a short look at the results,
specifically the benchmark of the n
dmd reference coff library problem solved?2.0.61 can use it? How
to use?
On Friday, 11 January 2013 at 13:50:33 UTC, monarch_dodra wrote:
I find that with LTR, you end up with a value (T.init), that
you never actually put into your array. IMO, that means
something went wrong somewhere. This is particularly relevant
with "++a[0]".
Not necessarily, as the computat
On 1/11/2013 4:14 PM, H. S. Teoh wrote:
Would an alias be appropriate in this case, so that we can put a
concrete name to the function return type? Or is that an abuse of alias?
Actually, that sounds like a good idea.
On 01/11/2013 08:53 AM, Don wrote:
Consider this code:
---
int[int] x;
int k = x[2] + 5; // Error, range violation. Makes sense.
x[2] = x[2] + 5; // But this works!!!
---
That is, x[2] doesn't exist, *unless you are about to assign to
it*.
What happens is:
1. lvalue index (create
On Fri, Jan 11, 2013 at 01:36:21PM -0800, Walter Bright wrote:
> On 1/11/2013 1:21 PM, Dmitry Olshansky wrote:
> >12-Jan-2013 00:50, Walter Bright пишет:
[...]
> >>buildTrie:
> >>
> >> Contains a number of functions that return auto, but no mention
> >>of what is returned. While I like auto, in
If your patch enforcing that a function tagged with noreturn
does not return (so core.stdc.stdlib.exit must be tagged with
noreturn)?
It isn't currently compulsory. Any noreturn function will still
compile without the attribute. If adopted, it would of course be
prudent to make stdlib.exit
On Jan 11, 2013, at 12:41 PM, H. S. Teoh wrote:
> On Fri, Jan 11, 2013 at 11:26:33AM -0800, Sean Kelly wrote:
>> On Jan 11, 2013, at 7:34 AM, Phil Lavoie wrote:
>>
>>> Anyone else finds themself desiring a "loadSymbol( void *
>>> whateverReturnedByLoadLib, string name )" function?
>>
>> Please
On 1/11/2013 1:21 PM, Dmitry Olshansky wrote:
12-Jan-2013 00:50, Walter Bright пишет:
On 1/11/2013 11:31 AM, Dmitry Olshansky wrote:
Anyway it's polished and ready for the good old collective destruction
called
peer review. I'm looking for a review manager.
Thank you for doing this. Some note
On Sat, Jan 12, 2013 at 01:06:30AM +0400, Dmitry Olshansky wrote:
> 12-Jan-2013 00:35, H. S. Teoh пишет:
> >On Fri, Jan 11, 2013 at 11:31:11PM +0400, Dmitry Olshansky wrote:
> >[...]
> >>Anyway it's polished and ready for the good old collective
> >>destruction called peer review. I'm looking for a
12-Jan-2013 00:50, Walter Bright пишет:
On 1/11/2013 11:31 AM, Dmitry Olshansky wrote:
Anyway it's polished and ready for the good old collective destruction
called
peer review. I'm looking for a review manager.
Thank you for doing this. Some notes:
Great bashing, thanks :)
struct Invers
12-Jan-2013 00:35, H. S. Teoh пишет:
On Fri, Jan 11, 2013 at 11:31:11PM +0400, Dmitry Olshansky wrote:
[...]
Anyway it's polished and ready for the good old collective
destruction called peer review. I'm looking for a review manager.
The code, including extra tests and a benchmark is here:
http
Chaiomanot:
Sometimes it's desirable to indirectly throw an exception,
especially if there's some work that needs to be done
specifically relating to the exception about to be thrown, but
you don't want to have to clutter your code with assert(false)
every time you do. For example:
void throwEi
12-Jan-2013 00:38, David Nadlinger пишет:
On Friday, 11 January 2013 at 19:31:13 UTC, Dmitry Olshansky wrote:
The code, including extra tests and a benchmark is here:
https://github.com/blackwhale/gsoc-bench-2012
Phew, that repository is quite a hefty checkout with all the example data.
Just
On 1/11/2013 11:31 AM, Dmitry Olshansky wrote:
Anyway it's polished and ready for the good old collective destruction called
peer review. I'm looking for a review manager.
Thank you for doing this. Some notes:
struct InversionList:
1. It implements length and empty, but otherwise does not
On Fri, Jan 11, 2013 at 12:35:42PM -0800, H. S. Teoh wrote:
[...]
> - It would also be nice if these functions can be made pure (I'm not
> sure I understand why checking the category of a character should be
> impure). The lack of nothrow I can understand, since the input
> character may be i
On Fri, Jan 11, 2013 at 11:26:33AM -0800, Sean Kelly wrote:
> On Jan 11, 2013, at 7:34 AM, Phil Lavoie wrote:
>
> > Anyone else finds themself desiring a "loadSymbol( void *
> > whateverReturnedByLoadLib, string name )" function?
>
> Please submit an enhancement request :-)
Is it safe to use vo
On Friday, 11 January 2013 at 19:31:13 UTC, Dmitry Olshansky
wrote:
The code, including extra tests and a benchmark is here:
https://github.com/blackwhale/gsoc-bench-2012
Phew, that repository is quite a hefty checkout with all the
example data.
Just for the fun of it, a completely irreprodu
On Fri, Jan 11, 2013 at 11:31:11PM +0400, Dmitry Olshansky wrote:
[...]
> Anyway it's polished and ready for the good old collective
> destruction called peer review. I'm looking for a review manager.
>
> The code, including extra tests and a benchmark is here:
> https://github.com/blackwhale/gsoc
Hello,
Is there any change would could be seeing a noreturn attribute or
way to hide a variable from the -vtls option in D in the near
future?
Sometimes it's desirable to indirectly throw an exception,
especially if there's some work that needs to be done
specifically relating to the exception ab
On Jan 11, 2013, at 7:34 AM, Phil Lavoie wrote:
> Anyone else finds themself desiring a "loadSymbol( void *
> whateverReturnedByLoadLib, string name )" function?
Please submit an enhancement request :-)
It's been long over due to present the work I did during the last GSOC
as it was a summer not winter of code after all. Unfortunately some
compiler bugs, a new job :) and unrelated events of importance have
postponed its release beyond measure.
Anyway it's polished and ready for the good old c
My understanding is that your understanding is somewhat different
from initial proposal but that is where discussion has flow to
since then and that makes me sad :)
They very reason to have staging is to have better replacement to
beta process which simply does not work good enough currently.
On Friday, 11 January 2013 at 09:13:56 UTC, Robert M. Münch wrote:
The Vortex library is a good one (if not the only really
matured one), actively developed and maintained. It's a
no-brainer to get it compiled, has a lot of examples,
test-suite, good docs etc. all there.
Back in the day when
Short comment about cherry pick - it is only bad in sense that it
creates separate untrackable commit with same content, which may
easily result in merging issues. If there is only one-way
direction for commit transitioning ( stuff goes from master to
staging and LTS and never goes back ) there is
On Thursday, 10 January 2013 at 20:08:36 UTC, bearophile wrote:
Walter Bright:
Any diagnostic that gives false positives should not be in the
compiler.
I generally agree.
So do you think spotting what's discussed here is going to
cause many false positives?
http://d.puremagic.com/issues/sh
On Friday, 11 January 2013 at 02:13:51 UTC, evilrat wrote:
On Thursday, 10 January 2013 at 23:54:41 UTC, Rob T wrote:
OK so these functions are not yet portable as stated in the
documentation, and currently only work for Windows (the docs
should be updated to state this).
I'm using Linux, s
And then you're right back where we started; Andrei's original
problem was how to just get a local copy of the latest and
greatest upstream without having merge conflicts, which (if you
don't have a separate local master) means using "git pull
--rebase -s recursive -X ours".
But: "rebase -X
On Fri, Jan 11, 2013 at 08:53:44AM +0100, Don wrote:
> Consider this code:
> ---
>int[int] x;
>
>int k = x[2] + 5; // Error, range violation. Makes sense.
>
>x[2] = x[2] + 5; // But this works!!!
> ---
>
> That is, x[2] doesn't exist, *unless you are about to assign to
> it*.
http:
On Friday, 11 January 2013 at 15:36:29 UTC, evilrat wrote:
On Friday, 11 January 2013 at 15:34:33 UTC, Phil Lavoie wrote:
On Thursday, 10 January 2013 at 07:35:54 UTC, Rob T wrote:
http://dlang.org/phobos/core_runtime.html#.Runtime.loadLibrary
I want to load shared libraries during runtime as
On Fri, Jan 11, 2013 at 08:47:19AM +0100, deadalnix wrote:
> On Thursday, 10 January 2013 at 22:28:46 UTC, H. S. Teoh wrote:
> >On Thu, Jan 10, 2013 at 11:18:07PM +0100, Era Scarecrow wrote:
> >>On Thursday, 10 January 2013 at 22:02:17 UTC, Dmitry Olshansky
> >>wrote:
> >>>+ user defined implicit c
On Friday, 11 January 2013 at 15:34:33 UTC, Phil Lavoie wrote:
On Thursday, 10 January 2013 at 07:35:54 UTC, Rob T wrote:
http://dlang.org/phobos/core_runtime.html#.Runtime.loadLibrary
I want to load shared libraries during runtime as plug-in's,
but the consensus seemed to indicate that DMD is
Excellent!
Thanks to both of you that was very instructive and you provided
answers to every one of my questions.
I might try to use the tools/options you suggested but I decided
to go the "load at runtime" way instead (or rather, in the
meantime). Since I got everything working it'd be hard
On Thursday, 10 January 2013 at 07:35:54 UTC, Rob T wrote:
http://dlang.org/phobos/core_runtime.html#.Runtime.loadLibrary
I want to load shared libraries during runtime as plug-in's,
but the consensus seemed to indicate that DMD is not yet ready
for this. I wonder if these functions provide an
On Friday, 11 January 2013 at 15:02:02 UTC, evilrat wrote:
*snip* also there is NO standard ABI for c++
Indeed, but "works for me" is good enough for me, and
pragma(mangle) is enough to make that happen at least.
One of the benefits of lower level languages is you have the
option of telling
On Friday, 11 January 2013 at 15:19:23 UTC, Adam D. Ruppe wrote:
On Friday, 11 January 2013 at 15:00:26 UTC, Daniel Murphy wrote:
And this is the only complete way, unless you can guarantee
the C++ calling conventions can be simulated with extern(C)
Guarantees aren't terribly important to me..
On Friday, 11 January 2013 at 15:00:26 UTC, Daniel Murphy wrote:
And this is the only complete way, unless you can guarantee the
C++ calling conventions can be simulated with extern(C)
Guarantees aren't terribly important to me... I'm doing a lot of
hacks as it is. Of course if the compiler ca
While we chat, the good Hara delivers :o)
https://github.com/D-Programming-Language/dmd/pull/1465
Bye,
bearophile
On Friday, 11 January 2013 at 14:27:35 UTC, Adam D. Ruppe wrote:
A solution to this specific thing is to add C++ constructor
mangling to the extern(C++) support.
But I think the general solution is pragma(mangle), that's been
discussed before.
there is some problem with C++ constructor(and
"Adam D. Ruppe" wrote in message
news:outrzhenaycnbogzw...@forum.dlang.org...
>
> A solution to this specific thing is to add C++ constructor mangling to
> the extern(C++) support.
>
And this is the only complete way, unless you can guarantee the C++ calling
conventions can be simulated with e
bottom line up front: I want pragma(mangle, "name")
I'd like to be able generate references to other functions in
templates and stuff
mixin template Template() {
extern(C) void test(); /* I want this to call test() */
}
struct Test {
mixin Template!();
void mything()
On Friday, 11 January 2013 at 13:27:46 UTC, deadalnix wrote:
On Friday, 11 January 2013 at 11:14:27 UTC, monarch_dodra wrote:
In particular, if you define an opIndexAssign, then the RHS
*has* to be evaluated first (from a "visual" point of view,
since LHS is pretty much "this").
//
a[0] =
On Friday, 11 January 2013 at 11:14:27 UTC, monarch_dodra wrote:
In particular, if you define an opIndexAssign, then the RHS
*has* to be evaluated first (from a "visual" point of view,
since LHS is pretty much "this").
//
a[0] = a[0]
//
Becomes
//
a.opIndexAssign(a[0], 0);
//
Don wrote:
> Consider this code:
> ---
>int[int] x;
>
>int k = x[2] + 5; // Error, range violation. Makes sense.
>
>x[2] = x[2] + 5; // But this works!!!
> ---
>
> That is, x[2] doesn't exist, *unless you are about to assign to
> it*.
> What happens is:
> 1. lvalue index (creates x[2
On Friday, 11 January 2013 at 10:59:00 UTC, monarch_dodra wrote:
It is meant to be an lvalue, and is the reason this is legal in
both C++ and D:
int main()
{
int a = 0;
a;
return 0;
}
OK, it seems I talked too fast here. Still it seems very weird to
me :D
On Friday, 11 January 2013 at 09:50:18 UTC, deadalnix wrote:
On Friday, 11 January 2013 at 08:55:55 UTC, Bernard Helyer
wrote:
I completely agree. Doesn't the spec say that relying on
the order of assignment evaluation is undefined?
After a long discussion with Andrei, it seems that it is left
On Friday, 11 January 2013 at 10:43:33 UTC, Jens Mueller wrote:
deadalnix wrote:
On Friday, 11 January 2013 at 10:16:28 UTC, Jens Mueller wrote:
>deadalnix wrote:
>>On Friday, 11 January 2013 at 08:55:55 UTC, Bernard Helyer
>>wrote:
>>>I completely agree. Doesn't the spec say that relying on
>>>
deadalnix wrote:
> On Friday, 11 January 2013 at 10:16:28 UTC, Jens Mueller wrote:
> >deadalnix wrote:
> >>On Friday, 11 January 2013 at 08:55:55 UTC, Bernard Helyer
> >>wrote:
> >>>I completely agree. Doesn't the spec say that relying on
> >>>the order of assignment evaluation is undefined?
> >>
>
On 2013-01-11 09:21, Walter Bright wrote:
"DLL" is Windows
"shared library" is Linux/OSX/FreeBSD
Some people have a tendency to mix the terms. I like to call it "dynamic
library" on all platforms.
--
/Jacob Carlborg
aa[key] = val;
should be evaluated:
1. aa
2. key
3. val
4. aa[key] = val <-- allocating slot and set to it
Kenji Hara
2013/01/11 18:56 "deadalnix" :
> On Friday, 11 January 2013 at 08:55:55 UTC, Bernard Helyer wrote:
>
>> I completely agree. Doesn't the spec say that relying on
>> the order of
On Friday, 11 January 2013 at 10:16:28 UTC, Jens Mueller wrote:
deadalnix wrote:
On Friday, 11 January 2013 at 08:55:55 UTC, Bernard Helyer
wrote:
>I completely agree. Doesn't the spec say that relying on
>the order of assignment evaluation is undefined?
After a long discussion with Andrei, it
On Friday, 11 January 2013 at 09:20:13 UTC, Jonathan M Davis
wrote:
On Friday, January 11, 2013 10:03:54 Don wrote:
That's my feeling too. I think that if we want to implement AAs
as a library type, we first need to eliminate all of the
semantics would be impossible to implement in a library.
deadalnix wrote:
> On Friday, 11 January 2013 at 08:55:55 UTC, Bernard Helyer wrote:
> >I completely agree. Doesn't the spec say that relying on
> >the order of assignment evaluation is undefined?
>
> After a long discussion with Andrei, it seems that it is left to
> right.
Then the spec should b
On Friday, 11 January 2013 at 07:31:45 UTC, Jacob Carlborg wrote:
On 2013-01-11 00:49, jerro wrote:
It sounds like you need to install libevent.
$ sudo port install libevent
If you're using macports.
Thanks, will try that
On Friday, 11 January 2013 at 08:55:55 UTC, Bernard Helyer wrote:
I completely agree. Doesn't the spec say that relying on
the order of assignment evaluation is undefined?
After a long discussion with Andrei, it seems that it is left to
right.
Shouldn't the rhs be evaluated before the lhs? Why would it be
undefined/unspecified/etc.?
"Don" wrote in message
news:imqicbgjotdtzfgwd...@forum.dlang.org...
> Consider this code:
> ---
>int[int] x;
>
>int k = x[2] + 5; // Error, range violation. Makes sense.
>
>x[2] = x[2] + 5; // But this works!!!
> ---
>
Definitely a bug.
"Phil Lavoie" wrote in message
news:cnfmacxdtgfmwmfzh...@forum.dlang.org...
> This websites recommends implib for the creation of import library
> therefore I have been using it. When I compile + link my code containing
> "extern( Windows )" function declarations, I get the following messages:
On Friday, January 11, 2013 10:03:54 Don wrote:
> That's my feeling too. I think that if we want to implement AAs
> as a library type, we first need to eliminate all of the
> semantics would be impossible to implement in a library.
Well, the AAs are _already_ a library type. That's a large part of
On 2013-01-05 22:33:45 +, Rob T said:
Funny you mentioned this, because a few years back when I thought BEEP
was a great idea, that's exactly what happened to me. I could not
easily get a grasp on how it worked, there were not even any examples.
What really killed it for me was the only BE
On 2013-01-05 19:54:11 +, Nick Sabalausky said:
This is the first I've heard of BEEP, but my guess so far is that the
main website for it:
http://beepcore.org/
Provides no explanation for how to use it beyond linking to a series of
long-winded and poorly-formatted RFCs, plus the site doesn
On 2013-01-05 20:15:31 +, Joakim said:
I think you mean "enhanced HTTP," as SPDY will be the first draft for HTTP 2.0:
http://lists.w3.org/Archives/Public/ietf-http-wg/2012OctDec/0447.html
Considering HTTP is now used by all kinds of apps that have nothing to
do with browsers or the web-
On 2013-01-05 03:45:11 +, Rob T said:
I forgot to add that you can always create D bindings directly to the
Vortex C library which will allow you to use BEEP with your D
applications via Vortex. That's one of the cool things about D, it is
fully compatible with the C ABI.
Yes, I know. Ne
On Friday, 11 January 2013 at 08:26:54 UTC, Jonathan M Davis
wrote:
On Friday, January 11, 2013 08:53:44 Don wrote:
Consider this code:
---
int[int] x;
int k = x[2] + 5; // Error, range violation. Makes sense.
x[2] = x[2] + 5; // But this works!!!
---
That is, x[2] doesn't exist,
See also:
http://d.puremagic.com/issues/show_bug.cgi?id=3825
Bye,
bearophile
Don wrote:
> Consider this code:
> ---
>int[int] x;
>
>int k = x[2] + 5; // Error, range violation. Makes sense.
>
>x[2] = x[2] + 5; // But this works!!!
> ---
I think the last statement is illegal. Because from
http://dlang.org/expression.html I extract:
The evaluation order of =
11-Jan-2013 05:43, Timon Gehr пишет:
On 01/10/2013 08:52 PM, Dmitry Olshansky wrote:
[snip]
Cool! I'd love to take even the very preliminary peek at the speed
profile of this CTFE engine.
If you are interested I'd love to test a small (the code though contains
a lot of static data) CTFE bench
On Friday, 11 January 2013 at 08:26:54 UTC, Jonathan M Davis
wrote:
On Friday, January 11, 2013 08:53:44 Don wrote:
Consider this code:
---
int[int] x;
int k = x[2] + 5; // Error, range violation. Makes sense.
x[2] = x[2] + 5; // But this works!!!
---
That is, x[2] doesn't exist,
On Friday, January 11, 2013 08:53:44 Don wrote:
> Consider this code:
> ---
> int[int] x;
>
> int k = x[2] + 5; // Error, range violation. Makes sense.
>
> x[2] = x[2] + 5; // But this works!!!
> ---
>
> That is, x[2] doesn't exist, *unless you are about to assign to
> it*.
>
> Wha
On 1/10/2013 11:44 PM, Jacob Carlborg wrote:
On 2013-01-11 07:26, F i L wrote:
Wait.. this was a bit unclear, but it sounded like you just said D's DLL
issues where fixed awhile ago.. Is D2 capable of correctly loading DLLs?
What's the situation with Linux?
I'm pretty sure that when he says "
On 2013-01-11 01:10, Martin Nowak wrote:
Right this is the same state on POSIX and of 2.061 all shared libraries
produced by dmd try to call a weakly linked `_d_dso_registry` upon
loading/unloading to pass EH and ModuleInfo tables.
https://github.com/D-Programming-Language/dmd/pull/1043/files#L0
75 matches
Mail list logo
