Am 05.01.2013 12:15, schrieb Jacob Carlborg:
On 2012-12-30 13:32, Benjamin Thaut wrote:
An article about runtime code reloading in the context of game
developement. A topic I'm currently working on in my spare time. I hope
it holds some valuable information for everyone working with D.
Am 05.01.2013 05:24, schrieb ixid:
On Monday, 31 December 2012 at 14:40:48 UTC, Benjamin Thaut wrote:
Am 31.12.2012 15:02, schrieb DypthroposTheImposter:
Do you find that D without GC is more effective than C++? Seems like
you would be stuck using structs which seems somewhat limiting, even
Benjamin Thaut:
In Summary it feels to me that GC free D is not important
to the community or the active contributors.
I think it will become more important for them, in future. At the
moment the work is mostly on finishing immutability, purity,
shared, and other parts of the core language,
On 2013-01-06 05:19, Pierre Rouleau wrote:
I know.
What I'm trying to see is what is the development *plan* for D2?
Something that would identify the future features to be implemented and
the planned targets/milestones for them.
I would assume that I am not alone in watching the D language
On 2013-01-06 11:37, Benjamin Thaut wrote:
I wouldn't say its moving away from it. Some recent changes to druntime
have made it significantly less leaking. But on the other hand a API
design like toString() which pretty much does leak in almost all cases
don't exactly help a GC free D. In
On 2013-01-06 11:30, Benjamin Thaut wrote:
Yes I know flectioned. But I did not require that much RTTI information.
No I'M not manually triggering the code for generating the RTTI. As
mentioned in the article it is done via the RTInfo template inside
object_.d / object.di which is automatically
On Sun, 2013-01-06 at 12:08 +0100, Jacob Carlborg wrote:
[…]
I've requested that for years, still nothing. Well that only thing I've
seen is that the change log used to say Under Construction: Shared
libraries for Linux. Still does for D1.
I know that the Go folk are of the view that shared
Am 06.01.2013 12:17, schrieb Jacob Carlborg:
On 2013-01-06 11:30, Benjamin Thaut wrote:
Yes I know flectioned. But I did not require that much RTTI information.
No I'M not manually triggering the code for generating the RTTI. As
mentioned in the article it is done via the RTInfo template
On Sat, 2013-01-05 at 12:57 -0500, Nick Sabalausky wrote:
[…]
That is a fair point. OTOH, Google (by their very nature) is dead-set on
things like making sure the web gets treated as an application platform
and getting people to store their personal data on Google's private
cloud (a moronic
On Sunday, 6 January 2013 at 04:19:53 UTC, Pierre Rouleau wrote:
I know.
What I'm trying to see is what is the development *plan* for
D2? Something that would identify the future features to be
implemented and the planned targets/milestones for them.
I would assume that I am not alone in
On 2013-01-06 12:27, Russel Winder wrote:
I know that the Go folk are of the view that shared libraries are an
abomination and all should be expunged from the universe; all Go
executables are statically linked.
Of course Linux, OS X, Solaris and AIX depend on shared libraries, but
maybe Google
Am Sun, 06 Jan 2013 12:10:38 +0100
schrieb Jacob Carlborg d...@me.com:
On 2013-01-06 11:37, Benjamin Thaut wrote:
I wouldn't say its moving away from it. Some recent changes to
druntime have made it significantly less leaking. But on the other
hand a API design like toString() which
I guess when we have custom allocators we can also provide toString
methods templated on allocators.
Custom allocators released together with HL3?
On Sun, 2013-01-06 at 12:56 +0100, Jacob Carlborg wrote:
[…]
I completely agree. We _need_ dynamic libraries. But the problem is that
someone just have to do it and Walter doesn't seem to be in a rush to
implement it.
Is Walter the only person who can implement this? I cannot commit to
doing
Am 06.01.2013 12:50, schrieb Jacob Carlborg:
On 2013-01-06 12:28, Benjamin Thaut wrote:
It does not exist. The current RTInfo template just outputs a null
pointer for every type.
Yes, but it still exists.
It is planned that the RTInfo template will be
used for a percise GC in the future.
On 2013-01-06 13:19, Benjamin Thaut wrote:
Here is the full implementation if you are interested:
https://github.com/Ingrater/druntime/blob/master/src/rtti.d
Thanks. Is that possible to do without having to modify the runtime?
--
/Jacob Carlborg
On 2013-01-06 13:20, Russel Winder wrote:
Is Walter the only person who can implement this? I cannot commit to
doing anything on this in the foreseeable short-, to medium-term future,
but is there anyone who can?
No, absolutely not. But no one has been willing to do it yet. Martin
Nowak
Am 06.01.2013 13:23, schrieb Jacob Carlborg:
On 2013-01-06 13:19, Benjamin Thaut wrote:
Here is the full implementation if you are interested:
https://github.com/Ingrater/druntime/blob/master/src/rtti.d
Thanks. Is that possible to do without having to modify the runtime?
No. The template
Am Sun, 06 Jan 2013 13:14:39 +0100
schrieb David d...@dav1d.de:
I guess when we have custom allocators we can also provide toString
methods templated on allocators.
Custom allocators released together with HL3?
A lot of things are blocked by custom allocators and this is indeed an
On Sun, 06 Jan 2013 11:32:28 +
Russel Winder rus...@winder.org.uk wrote:
On Sat, 2013-01-05 at 12:57 -0500, Nick Sabalausky wrote:
[…]
Also I think another part of what makes Google (and Apple) so
dangerous is that unlike MS, most people are still hailing them as
wonderful and
Pierre Rouleau, el 5 de January a las 23:19 me escribiste:
On 13-01-05 4:01 PM, Walter Bright wrote:
On 1/5/2013 10:06 AM, Pierre Rouleau wrote:
On 13-01-05 5:39 AM, Walter Bright wrote:
On 1/5/2013 1:30 AM, Pierre Rouleau wrote:
I noticed that D 2.062 has no new features. What would it
Walter Bright, el 4 de January a las 10:58 me escribiste:
On 1/4/2013 6:02 AM, Leandro Lucarella wrote:
Walter Bright, el 3 de January a las 23:03 me escribiste:
On 1/3/2013 9:49 PM, Jonathan M Davis wrote:
but other lines like
$(LI std.string: $(RED The implementations of
Pierre Rouleau, el 4 de January a las 11:59 me escribiste:
On 13-01-04 3:45 AM, Walter Bright wrote:
On 1/4/2013 12:16 AM, eles wrote:
Two concrete examples:
http://d.puremagic.com/issues/show_bug.cgi?id=5992
is described in the list as: Phobos Win64 - D2 ; At least, change
its title
Just finished making the parser analyze UDA syntax flawlessly +
Slight profiling statistics display support (dmd exclusive,
unfortunately).
Ah, before I forget it: No, the 'deprecated' attribute syntax à la
[...] void foo() {}
is not supported, only
@... void bar() {}
:-)
On Sunday, 6 January 2013 at 17:10:17 UTC, alex wrote:
Just finished making the parser analyze UDA syntax flawlessly +
Slight profiling statistics display support (dmd exclusive,
unfortunately).
Ah, before I forget it: No, the 'deprecated' attribute syntax à
la
[...] void foo() {}
is not
On Sunday, 6 January 2013 at 17:15:30 UTC, nazriel wrote:
On Sunday, 6 January 2013 at 17:10:17 UTC, alex wrote:
Just finished making the parser analyze UDA syntax flawlessly
+ Slight profiling statistics display support (dmd exclusive,
unfortunately).
Ah, before I forget it: No, the
Oh, no you actually can type
deprecated(Don't do this because!) void oldFoo() {}
now.
You can? Wow, yet another change that was not in the docs? I'm becoming
bitter, here.
With the 'deprecated' attribute syntax I meant this [..] attribute syntax,
nothing else. :)
OK.
Good job,
On Sunday, 6 January 2013 at 17:18:33 UTC, alex wrote:
On Sunday, 6 January 2013 at 17:15:30 UTC, nazriel wrote:
On Sunday, 6 January 2013 at 17:10:17 UTC, alex wrote:
Just finished making the parser analyze UDA syntax flawlessly
+ Slight profiling statistics display support (dmd exclusive,
On 13-01-06 11:43 AM, Leandro Lucarella wrote:
Pierre Rouleau, el 5 de January a las 23:19 me escribiste:
On 13-01-05 4:01 PM, Walter Bright wrote:
On 1/5/2013 10:06 AM, Pierre Rouleau wrote:
On 13-01-05 5:39 AM, Walter Bright wrote:
On 1/5/2013 1:30 AM, Pierre Rouleau wrote:
I noticed
06-Jan-2013 14:37, Benjamin Thaut пишет:
Am 05.01.2013 05:24, schrieb ixid:
On Monday, 31 December 2012 at 14:40:48 UTC, Benjamin Thaut wrote:
Am 31.12.2012 15:02, schrieb DypthroposTheImposter:
Do you find that D without GC is more effective than C++? Seems like
you would be stuck using
On Sunday, 6 January 2013 at 17:37:05 UTC, Philippe Sigaud wrote:
Oh, no you actually can type
deprecated(Don't do this because!) void oldFoo() {}
now.
You can? Wow, yet another change that was not in the docs? I'm
becoming
bitter, here.
With the 'deprecated' attribute syntax I meant
On 13-01-06 11:40 AM, Leandro Lucarella wrote:
Pierre Rouleau, el 4 de January a las 11:59 me escribiste:
On 13-01-04 3:45 AM, Walter Bright wrote:
On 1/4/2013 12:16 AM, eles wrote:
Two concrete examples:
http://d.puremagic.com/issues/show_bug.cgi?id=5992
is described in the list as:
On Sun, 2013-01-06 at 11:42 -0500, Nick Sabalausky wrote:
[…]
Yea, I've noticed the same thing :( People are so enamored with their
iDevices, that they think Apple can do no wrong. At least that's the
only explanation I can think of.
Perhaps Apple employees visit everyone who buys an Apple
On Sun, Jan 6, 2013 at 6:56 PM, Pierre Rouleau prouleau...@gmail.comwrote:
So, again, this is why I was asking whether you guys thought it would
be a good idea for me to start a discussion somewhere in one of the D
mailing lists, to gather the list of new features planned for the future
On Sun, Jan 6, 2013 at 6:49 PM, Dmitry Olshansky dmitry.o...@gmail.comwrote:
Regarding toString there is a better signature that avoids useless
allocations:
void toString(scope void delegate(const (char)[]) sink);
It takes a delegate to output string representation directly to the
On 13-01-03 1:37 PM, Johannes Pfau wrote:
Am Thu, 03 Jan 2013 17:43:03 +0100
schrieb bearophile bearophileh...@lycos.com:
I agree. But we should probably start shipping minor releases.
+1
That would also enhance the visibility of the new language features in
major releases for the
06-Jan-2013 23:55, Philippe Sigaud пишет:
On Sun, Jan 6, 2013 at 6:49 PM, Dmitry Olshansky dmitry.o...@gmail.com
mailto:dmitry.o...@gmail.com wrote:
Regarding toString there is a better signature that avoids useless
allocations:
void toString(scope void delegate(const (char)[])
On 13-01-06 2:52 PM, Philippe Sigaud wrote:
On Sun, Jan 6, 2013 at 6:56 PM, Pierre Rouleau prouleau...@gmail.com
mailto:prouleau...@gmail.com wrote:
So, again, this is why I was asking whether you guys thought it
would be a good idea for me to start a discussion somewhere in one
of
The main newsgroup. Normally, D.announce should not contain this kind of
conversation. It's supposed to be a low-bandwidth list for announcing
projects and releases.
On 13-01-06 2:52 PM, Philippe Sigaud wrote:
As a token of goodwill, I'm willing to write a short text describing the
new release and plans for the next ones, except I don't even *know* what
the new release brought or what the next one will be.
I, for one, would be very interested. Even if
On 2013-01-06 16:20, Pierre Rouleau wrote:
Is there a file somewhere that lists all requested features, under
development features? Or the various mailing lists the only source of
information?
There is some information at the wiki, the DIP's.
--
/Jacob Carlborg
On Sun, 06 Jan 2013 19:25:48 +
Russel Winder rus...@winder.org.uk wrote:
On Sun, 2013-01-06 at 11:42 -0500, Nick Sabalausky wrote:
[…]
Yea, I've noticed the same thing :( People are so enamored with
their iDevices, that they think Apple can do no wrong. At least
that's the only
Am 06.01.2013 20:55, schrieb Philippe Sigaud:
On Sun, Jan 6, 2013 at 6:49 PM, Dmitry Olshansky dmitry.o...@gmail.com
mailto:dmitry.o...@gmail.com wrote:
Regarding toString there is a better signature that avoids useless
allocations:
void toString(scope void delegate(const (char)[])
07-Jan-2013 00:02, Dmitry Olshansky пишет:
06-Jan-2013 23:55, Philippe Sigaud пишет:
On Sun, Jan 6, 2013 at 6:49 PM, Dmitry Olshansky dmitry.o...@gmail.com
mailto:dmitry.o...@gmail.com wrote:
Regarding toString there is a better signature that avoids useless
allocations:
void
On 1/6/2013 3:56 AM, Jacob Carlborg wrote:
I completely agree. We _need_ dynamic libraries. But the problem is that someone
just have to do it and Walter doesn't seem to be in a rush to implement it.
It's actually completely implemented in the compiler. I've spend considerable
effort making
On 1/6/2013 4:20 AM, Russel Winder wrote:
For the Go folks, it is all about issues with garbage collection and
thread management,
It is for D as well (along with TLS). Unfortunately, the druntime implementation
of these is complex, and I do not understand it.
On 1/6/2013 4:32 AM, Jacob Carlborg wrote:
I have tried myself a couple of times but there has always been some issue with
the compiler that needs to be fixed or implemented.
I have fixed every single PIC implementation compiler problem that has been
brought to my attention. If there are
On 1/6/2013 7:20 AM, Pierre Rouleau wrote:
Is there a file somewhere that lists all requested features, under development
features? Or the various mailing lists the only source of information?
On Sunday, January 06, 2013 15:15:23 Walter Bright wrote:
On 1/6/2013 4:20 AM, Russel Winder wrote:
For the Go folks, it is all about issues with garbage collection and
thread management,
It is for D as well (along with TLS). Unfortunately, the druntime
implementation of these is complex,
On 13-01-06 6:21 PM, Walter Bright wrote:
On 1/6/2013 7:20 AM, Pierre Rouleau wrote:
Is there a file somewhere that lists all requested features, under
development
features? Or the various mailing lists the only source of information?
On Sunday, January 06, 2013 18:49:18 Pierre Rouleau wrote:
On 13-01-06 6:21 PM, Walter Bright wrote:
On 1/6/2013 7:20 AM, Pierre Rouleau wrote:
Is there a file somewhere that lists all requested features, under
development
features? Or the various mailing lists the only source of
On 1/6/2013 3:47 PM, Jonathan M Davis wrote:
Does this mean that we need Sean Kelly to do it? If so, we're in trouble,
because he seems to be _very_ busy these days and is generally uninvolved. I
don't know if anyone else knows the code well enough to attempt it. Hopefully,
someone does or is
On 1/6/2013 3:49 PM, Pierre Rouleau wrote:
If this list already contains all (does it?) of what is currently identified
then is there some criteria one can use to try to infer what will be implemented
in the next release? Or is it just first come first served where the solved
enhancements
Pierre Rouleau, el 6 de January a las 12:56 me escribiste:
Yeah, that's another issue too. Having mutating release notes is awful
and a PR disaster. Users only see the changelog once, assuming is
immutable, because one thinks that releases are immutable and complete
(those are very
On 1/6/2013 8:42 AM, Nick Sabalausky wrote:
Like browsers, for instance. When Microsoft had their browser merely
uninstallable and set as the *initial* default browser, the DOJ went
apeshit, nevermind the fact that MS did *nothing* to prevent people
from downloading and using competing browsers.
On 1/6/2013 4:25 PM, Leandro Lucarella wrote:
I really hope at some point this will be addressed, and I think other
areas of the development process have been improved enough to think this
is a good moment to do so, but first management (OK, I will say it:
Walter) have to be convinced (or
On Sunday, January 06, 2013 17:28:57 Brad Roberts wrote:
Does anyone know of any mechanism for getting people to do what needs to be
done vs what they want to do that doesn't involve paying them? The only
long term successes I can point to all involve companies.
You'd have to look at major
On 1/6/2013 5:41 PM, Jonathan M Davis wrote:
On Sunday, January 06, 2013 17:28:57 Brad Roberts wrote:
Does anyone know of any mechanism for getting people to do what needs to be
done vs what they want to do that doesn't involve paying them? The only
long term successes I can point to all
The slides:
https://speakerd.s3.amazonaws.com/presentations/505f7d17ccf4a50002011800/emerging-languages.pdf
Bye,
bearophile
Walter Bright, el 6 de January a las 16:36 me escribiste:
On 1/6/2013 3:49 PM, Pierre Rouleau wrote:
If this list already contains all (does it?) of what is currently identified
then is there some criteria one can use to try to infer what will be
implemented
in the next release? Or is it
On 13-01-06 7:36 PM, Walter Bright wrote:
On 1/6/2013 3:49 PM, Pierre Rouleau wrote:
If this list already contains all (does it?) of what is currently
identified
then is there some criteria one can use to try to infer what will be
implemented
in the next release? Or is it just first come first
On 13-01-06 8:41 PM, Jonathan M Davis wrote:
On Sunday, January 06, 2013 17:28:57 Brad Roberts wrote:
Does anyone know of any mechanism for getting people to do what needs to be
done vs what they want to do that doesn't involve paying them? The only
long term successes I can point to all
On Sunday, January 06, 2013 21:15:43 Pierre Rouleau wrote:
So, given that enhancements are identified in Bugzilla, is there a
review process? Are ticket priorities and vote used? Who decides what
is the priority of an enhancement? Who assigns them?
There's pretty much never any assigning
On 1/6/2013 6:15 PM, Pierre Rouleau wrote:
So, given that enhancements are identified in Bugzilla, is there a review
process? Are ticket priorities and vote used? Who decides what is the priority
of an enhancement? Who assigns them?
Pretty much anyone who wants to take one of them on does
On Sunday, January 06, 2013 21:22:18 Pierre Rouleau wrote:
Is this something that the most influential people in the D project want
to fix?
What exactly do you want fixed? Sure, it would be great if we could know when
certain things are going to be implemented or fixed, but without people to
On 13-01-06 9:45 PM, Jonathan M Davis wrote:
On Sunday, January 06, 2013 21:22:18 Pierre Rouleau wrote:
Is this something that the most influential people in the D project want
to fix?
What exactly do you want fixed?
Really, I would like to be able to start using D at work. And be in a
On 13-01-06 9:35 PM, Jonathan M Davis wrote:
On Sunday, January 06, 2013 21:15:43 Pierre Rouleau wrote:
So, given that enhancements are identified in Bugzilla, is there a
review process? Are ticket priorities and vote used? Who decides what
is the priority of an enhancement? Who assigns
On 13-01-06 9:41 PM, Walter Bright wrote:
On 1/6/2013 6:15 PM, Pierre Rouleau wrote:
So, given that enhancements are identified in Bugzilla, is there a review
process? Are ticket priorities and vote used? Who decides what is
the priority
of an enhancement? Who assigns them?
Pretty much
On 1/6/2013 7:30 PM, Pierre Rouleau wrote:
Understood, that's pretty much always the case for any programming language.
Now, for someone from the outside, how would someone know what are the latest
features?
In the changelog, click on New/Changed Features.
Would it be possible to identify
On 2013-01-07 00:19, Walter Bright wrote:
I have fixed every single PIC implementation compiler problem that has
been brought to my attention. If there are others, I am not aware of
them. Please let me know the bugzilla issue numbers for any I have missed.
I know you have. The problem is that
70 matches
Mail list logo
