Gets better and better!
Makes me wonder though: if this works, may be it is possible to
provide a context helper with mixin resulting code if all it
parameters are already defined? Similar to C macro expansion
helper in Eclipse.
On Sunday, 27 January 2013 at 12:05:28 UTC, alex wrote:
On Sunday, 27 January 2013 at 11:31:58 UTC, Dicebot wrote:
Gets better and better!
Makes me wonder though: if this works, may be it is possible
to provide a context helper with mixin resulting code if all
it parameters are already
Small notification about the topic. No point to use old wiki for
those anymore I suppose.
I have created a pull request to update links on front page:
https://github.com/D-Programming-Language/d-programming-language.org/pull/242
http://wiki.dlang.org/DIP22
There are two important issues with current protection attribute
design:
* Senseless name clashes between private and public symbols
* No way to specify internal linkage storage class
This DIP addresses both of them with two decoupled proposals:
* Change of private
On Monday, 28 January 2013 at 17:18:27 UTC, eles wrote:
On Monday, 28 January 2013 at 17:05:38 UTC, Dicebot wrote:
http://wiki.dlang.org/DIP22
Error on that page (for C++):
public
Default one, if you can see symbol - you can access it
That is true only for structs. For classes, private
On Monday, 28 January 2013 at 17:36:58 UTC, Timon Gehr wrote:
Fixing private is enough.
Not a fan of the static thing at all. It is a great thing that
the static attribute actually has a consistent meaning in D.
mixin template X(){
static int x = 2;
}
class C{
mixin X; // x is a
Fixing private is enough.
...
No need to screw this up.
By the way, do you oppose exactly static keyword usage or
ability to mark symbols for internal linkage at all? How about
something like @internal?
On Tuesday, 29 January 2013 at 16:44:56 UTC, Timon Gehr wrote:
On 01/29/2013 11:29 AM, Dicebot wrote:
Fixing private is enough.
...
No need to screw this up.
By the way, do you oppose exactly static keyword usage or
ability to
mark symbols for internal linkage at all? How about something
Case 1 (binary level, C + D):
- sample.d -
module sample;
private int func() { return 42; }
--
- oops.c -
#include stdio.h
extern int _D6sample4funcFZi();
void* _Dmodule_ref = 0;
void* _D15TypeInfo_Struct6__vtblZ = 0;
void _Dmain() { }
int main()
{
long value =
On Wednesday, 30 January 2013 at 05:29:14 UTC, Jesse Phillips
wrote:
And this results in people writing code that ...? Is there an
example where you can break code in another module by changing
something marked as private?
Examples separated:
On Wednesday, 30 January 2013 at 20:22:11 UTC, Jacob Carlborg
wrote:
If you have a public and a private function in the same module,
it's possible to implement the two functions in two separate
object files. The private function must then be available in
the object file to link the program
On Wednesday, 30 January 2013 at 11:39:26 UTC, Timon Gehr wrote:
On 01/30/2013 10:42 AM, Dicebot wrote:
...
That was the most uneasy part of proposal. I have been
thinking for few
hours about it, considering different options. In the end, I
have
decided that it is only confusing to one coming
On Thursday, 31 January 2013 at 20:43:14 UTC, Jesse Phillips
wrote:
I meant more that these questions should be answered the DIP
page.
Sure, I just want to gather more opinions before doing version 2
of DIP. Most likely will gather all together this weekend.
My assumption is that I don't
OK, I have finally got to it and separated proposal into
http://wiki.dlang.org/DIP22 (private) and
http://wiki.dlang.org/DIP22.1 (internal linkage). Private
proposal is updated according to this discussion. Internal
linkage proposal is only separated, with no real changes,
because I am not
I have considered writing and proposing one, but it is a very low
priority to me now, sorry. Should be not that difficult
considering driver for MySQL can be used as an example (
http://registry.vibed.org/packages/mysql-native ), just
time-consuming.
On Thursday, 14 February 2013 at 18:34:44 UTC, ponce wrote:
On Thursday, 14 February 2013 at 15:48:03 UTC, F i L wrote:
The line-up looks great! Unfortunately I cannot attend :(
Everyone's talks looks awesome. Looks like it will be a great
few days, have fun folks! (and please record it for us
What has happened with dpaste recently?
Paste itself does work, but compilation does not anymore.
On Sunday, 24 February 2013 at 11:31:01 UTC, deed wrote:
On Saturday, 23 February 2013 at 14:27:58 UTC, Dicebot wrote:
What has happened with dpaste recently?
Paste itself does work, but compilation does not anymore.
It has been like that since this thread was started.
Ugh, I have noticed
On Wednesday, 27 February 2013 at 01:56:35 UTC, nazriel wrote:
Backend's server migration required to redesign and
re-implement whole infrastructure.
Unfortunately I had some issues with health so it took some
time.
We are back now. There are some things I still need to do, like
32bit
As far as I have understood, Xamarin Studio is the name for
latest MonoDevelop branch. At least it is installed in Arch Linux
under the name monodevelop with version 4.x
AUR package https://aur.archlinux.org/packages/vibed has been
updated.
to Dicebot for
digging up some
documents of how Nginx does this).
Awesome! I had hoped you would add multi-threaded processing.
I'm looking forward to playing with this.
How does it work? I added this to HttpServerSettings:
options |= HttpServerOption.distribute
But it doesn't seem to use
I have done a few performance tests and I am afraid I do not like
where it gets. Not enough data for public review has been
gathered yet, so I have sent my concerns via e-mail.
But to sum up short, feels like GC issues start to hit hard at
higher concurrency levels.
On Wednesday, 3 April 2013 at 19:07:39 UTC, Vadim Lopatin wrote:
I don't see what to simplify in markup like this:
...
You may implement approach similar to one used in vibe.d
http.rest and http.form modules. Some specific examples are
described by Jacob, but, in general, in results in 3
On Friday, 5 April 2013 at 07:32:55 UTC, Vadim Lopatin wrote:
Looks ugly, but I tried `typedef string String`, but it is
deprecated; `alias string String` cannot be distinguished from
just string. How to define String better? Is there a good way
to define String to be compatible with string,
On Friday, 5 April 2013 at 09:26:30 UTC, Vadim Lopatin wrote:
On Friday, 5 April 2013 at 07:57:37 UTC, Dicebot wrote:
On Friday, 5 April 2013 at 07:32:55 UTC, Vadim Lopatin wrote:
Looks ugly, but I tried `typedef string String`, but it is
deprecated; `alias string String` cannot
On Friday, 5 April 2013 at 15:20:06 UTC, Jacob Carlborg wrote:
On 2013-04-05 16:03, Vadim Lopatin wrote:
2) Read/write property
@property T someProperty() { ... }
@property xxx someProperty(T value) { ... }
treated as property with name 'someProperty'
BTW, I don't know how to check
On Friday, 5 April 2013 at 16:41:53 UTC, Vadim Lopatin wrote:
I'm iterating through class members using __traits(allMembers,
T), then accessing member using _traits(getMember,T,memberName)
I'm not sure which one of the members with the same name will
be returned by getMember... Property
On Tuesday, 9 April 2013 at 06:42:34 UTC, Rory McGuire wrote:
Could we not still run the basics of the program minus the
funding? Perhaps
there are still students and mentors that would be interested
in contributing their time for their name down in the history
of D. :)
We could call it
On Tuesday, 9 April 2013 at 16:32:51 UTC, Brad Roberts wrote:
In what way would this differ from the normal every day
experience of hey, I'm going to work on X, could I ask for
some help with the design of it?
You are somewhat guaranteed to have a person you can ask for help
and expect at
http://vibed.org/download links are not updated, still 0.7.14
there.
On Wednesday, 8 May 2013 at 04:46:30 UTC, Andrei Alexandrescu
wrote:
Go to http://dconf.org/talks/bright.html
Andrei
Ugh, that may sound boring and naive, but why no YouTube mirror?
On Wednesday, 8 May 2013 at 12:48:56 UTC, Namespace wrote:
I've grabbed the .pdf above from slideshare.net, so I guess
not.
Too bad. I'd like to read the slides of 'Copy and Move
Semantics'.
Patience! :) I'd like read _all_ main schedule slides, they sound
so yummy. (opening keynote is good
On Wednesday, 8 May 2013 at 15:11:32 UTC, Andrei Alexandrescu
wrote:
I chose dailymotion.com because it accepts videos of the
appropriate size and duration. Are there better sites I should
use?
Thanks,
Andrei
YouTube with verified account. Problem solved! David even has
already created
On Sunday, 12 May 2013 at 00:22:58 UTC, Andrei Alexandrescu wrote:
On 5/11/13 7:39 PM, Nick Sabalausky wrote:
Furthermore, my whole point was nothing more than to merely
suggest
that *maybe* the delay should simply be somewhat less, *not* a
demand
or expectation, and *not* even a suggestion
On Monday, 13 May 2013 at 12:01:54 UTC, Andrei Alexandrescu wrote:
Watch, discuss, vote up!
http://reddit.com/r/programming/comments/1e8mwq/dconf_2013_day_1_talk_3_distributed_caching/
Andrei
On promising consequence of such compiler daemonization I have
always had in mind since got
On Wednesday, 15 May 2013 at 05:08:47 UTC, Walter Bright wrote:
http://ftp.digitalmars.com/dmd2beta.zip
It's time we start the process. If you wish to be a part of it,
join the dmd-beta mailing list.
http://wiki.dlang.org/Release_Process
May we hope?
On Tuesday, 14 May 2013 at 19:57:12 UTC, Guillaume Chatelet wrote:
Dicebot, Sönke, how about a vibe.d based compiler ? :P
I don't think networking part of of distributed compiler will be
that demanding :) It is more about good pipe-lining, like
described in Robert presentation. Concurrency
P.S. And even easier if std.concurrency starts to work over
network sockets :P
On Friday, 10 May 2013 at 12:08:10 UTC, Andrei Alexandrescu wrote:
...
After some more thinking on topic I get the feeling that this is
yet another case when having defined and working scope for
function parameters would have been extremely useful.
Lets imagine some string processing
On Wednesday, 15 May 2013 at 17:32:14 UTC, Jonathan M Davis wrote:
You probably should actually quote part of the message so that
it's easier to
figure out exactly which message you're replying to it.
It is hard to quote the video :) I was referring to the part
starting somewhere here:
On Thursday, 16 May 2013 at 10:13:28 UTC, Regan Heath wrote:
...
I agree that this is a caller responsibility. What leaves me in
doubts is how this responsibility is enforced though. With const
nothing in type system prevents caller to violate that contract
and mutate data during function
On Thursday, 16 May 2013 at 19:52:51 UTC, Jonathan M Davis wrote:
On Thursday, May 16, 2013 11:13:27 Regan Heath wrote:
So, who's responsibility is it to ensure the function/method
call executes
without errors caused by mutable shared data?
I think that for the most part, the question of
I have reached conceptual agreement with dmd package maintainer
(Sven-Hendrik Haase), new PKGBUILD's are written and change is
planned together with 2.063 release.
Important stuff to be aware of (mostly important to AUR
packagers):
* dmd now provides virtual package d-compiler of version
can have a look at PKGBUILD drafts for upcoming packages here
: https://github.com/Dicebot/Arch-PKGBUILDs for insight. Actually
simply changing version there from master to 2.063 and back
makes all the difference between dmd-git and upcoming release : )
On Saturday, 18 May 2013 at 19:19:10 UTC, Iain Buclaw wrote:
Agreed. I had this discussion recently too along the topic of:
Should we
allow people to install libphobos/libdruntime in a common
library
directory, or keep it private as an integral part of the
compiler? IMO,
giving given it's
Can't wait to see a prototype for D2 :) I have a feeling that
this may solve at least some of vibe.d latency issues at high
concurrency levels.
On Tuesday, 21 May 2013 at 10:12:41 UTC, Nick Sabalausky wrote:
// Psuedocode
START TRANSACTION;
scope(fail) ROLLBACK;
scope(exit) COMMIT;
Nice :)
You may have meant scope(success) COMMIT;, scope(exit) is
executed on both failure and success.
Also, about that publicity discussion. Currently only way to
read D-related announcement on dlang.org (if you are not a forum
explorer) is embedded Twitter stuff. It is not very informative
and does not bring attention. What about doing proper news feed
page on dlang.org (with RSS, yay!) and
Eh, official definition of breaking change keeps breaking my
heart. But I guess this is a mindset set in stone now and
changing it is close to impossible.
One positive thing to add, though: a question was asked about
automatic tools that can make required changes automatically when
something
On Wednesday, 22 May 2013 at 20:51:34 UTC, Walter Bright wrote:
...
Really glad to see this :)
On Thursday, 23 May 2013 at 12:18:14 UTC, Joseph Rushton Wakeling
wrote:
On Wednesday, 22 May 2013 at 13:44:10 UTC, Dicebot wrote:
Eh, official definition of breaking change keeps breaking my
heart. But I guess this is a mindset set in stone now and
changing it is close to impossible.
Can
something I may have actually used in real code writing a
low-level networking library:
struct Packet
{
immutable etherType = 0x0800; // IPv4 by default;
// ...
this(bool IPv6)
{
if (!IPv6)
return; // fine
On Thursday, 23 May 2013 at 14:58:01 UTC, Steven Schveighoffer
wrote:
Seems like const qualifier for members is simply ignored inside
the ctor, it should only be ignored until it is set, or until
it is used.
I am quite sure I have seen it (mutability of immutable in
constructor) guaranteed
On Thursday, 23 May 2013 at 16:01:56 UTC, Don wrote:
That's better, but it's still not a convincing example.
I don't see why you cannot remove the intializer, and write:
this(bool IPv6)
{
if (!IPv6)
etherType = 0x0800;
else
etherType = 0x86DD;
...
}
Because then you
I like it. A lot, probably.
When semantics of something does change it makes a lot sense to
decouple deprecation of old behavior and introduction of new. I
may even say it is worth using as a default approach for a
semantics change in similar cases ;)
On Friday, 24 May 2013 at 00:01:20 UTC,
On Friday, 24 May 2013 at 11:57:53 UTC, Don wrote:
...
I have finally understood your point about default initializer vs
changing T.init :) It was not that easy because there are no
similar terms in other languages. Anyway, it does make sense.
Somehow separating concept of compile-time
On Friday, 24 May 2013 at 13:58:32 UTC, Steven Schveighoffer
wrote:
Being able to dictate the .init data is very powerful and
useful. You can't remove that feature.
Sure, I completely agree, thus the idea adding of CTFE-able
constructor which will become the T.init for structs.
But the
On Sunday, 26 May 2013 at 00:57:23 UTC, Andrei Alexandrescu wrote:
...
It seems like Sociomantic will get at least one :) Funny, but
idea that they are hiring never came to my mind until this DConf.
On Saturday, 25 May 2013 at 05:32:28 UTC, deadalnix wrote:
They define a default value for the field. The constructor can
override it. It is expected that a constructor is able to
construct an object.
Yes, I know. Actually, I have been saying it earlier in this
topic. So what? :)
On Monday, 27 May 2013 at 07:32:15 UTC, TommiT wrote:
I don't see a reason why we couldn't have both ways (1. member
initializers and 2. CTFE-able default constructor) for defining
the init state of structs. Probably the sensible thing would be
to make all member initializers illegal iff a
On Monday, 27 May 2013 at 17:08:19 UTC, Leandro Lucarella wrote:
You can achieve the same with:
if (!IPv6)
etherType = 0x0800;
else
...
There is no need to double-initialize a immutable value.
As I have already
On Friday, 31 May 2013 at 00:28:58 UTC, Jesse Phillips wrote:
Perfect chance to try out the new release process. Patch 2.063
and release 2.063.1.
Actually v2.063.1 is the current one, check the dmd tags ;)
It will be v2.063.2
P.S. It has made life of linux packagers SOOO much easier ^_^
On Thursday, 30 May 2013 at 22:41:08 UTC, Rob T wrote:=
Prior to issuing a release like this, it should instead be made
public as a stable release candidate with full installer on
the downloads page for review by anyone. After the bugs are
worked out and some time has elapsed, the stable RC is
I want to express my sincere gratitude to everyone who has been
involved in doing this release. It is a major breakthrough in D
development and release process and a solid step towards truly
mature project.
Really, a lot of small but important changes have just happened
that make this
On Friday, 31 May 2013 at 09:08:17 UTC, Leandro Lucarella wrote:
This is just plain and completely wrong. I don't know many
big-ish
opensource projects that doesn't have release candidates, and I
haven't
see any distribution targeted at end users using release
candidates.
Have you ever see a
On Friday, 31 May 2013 at 14:08:18 UTC, Leandro Lucarella wrote:
In mature projects RC does not differ that much from actual
release
other than by extra regression fixes. But for D process is not
THAT
smooth enough and it will take some time to settle things down.
This is pretty much how it
On Friday, 31 May 2013 at 14:08:17 UTC, Leandro Lucarella wrote:
And I don't mean to minimize the incredible breakthrough
concerning the
release process in this cycle, just pointing out places were we
can
still do better :)
Btw, I have included minor version number into Arch Linux package
On Thursday, 6 June 2013 at 10:50:30 UTC, Marco Leise wrote:
Yes please, this is holding me back from updating the Gentoo
package for dmd 2.063. (Unless I want to add that missing file
as a patch.)
Why not use git tag instead?
On Thursday, 13 June 2013 at 08:16:56 UTC, Peter Alexander wrote:
Visual Studio constantly crashes for me at work, and I can
imagine MonoDevelop and Eclipse being similar, but simpler
editors like Sublime Text, TextMate, vim, emacs etc. shouldn't
crash. I've been using Sublime Text for years
On Thursday, 13 June 2013 at 09:06:00 UTC, Don wrote:
Mono-D and Eclipse DDT both have major problems with long
pauses while typing (eg 15 seconds unresponsive) and crashes.
Both of them even have modules of death where just viewing
the file will cause a crash. If you're unlucky enough to get
On Thursday, 13 June 2013 at 13:22:23 UTC, Don wrote:
Guys, this wasn't even part of the talk. The point I made in
the talk is: at the moment, IDE bugs are much, much worse than
compiler bugs.
Those IDEs are in an alpha state at best. They are not in a
state where you can just submit bug
On Thursday, 13 June 2013 at 22:30:25 UTC, Peter Alexander wrote:
What can gdb do in particular that Visual Studio can't?
Not trying to troll, I'm genuinely curious. I googled for
advanced gdb tricks to try and find some of the more advanced
stuff, but it was all simple things that Visual
Have finally watched it. Great talk and good jokes! :)
One topic I'd like to hear more about is memory management
techniques. It was told that only very small amount of garbage is
generated and managed by GC, most code avoids heap allocations at
all. Is this somehow enforced (tooling, code
Slowly catching up with published videos :)
This has kind of convinced me that once D gets wider usage, tools
similar to AnalyzeD may become de-facto standard part of any
production toolchain, with a configurable rule set. D is complex
and multi-paradigm language (which rocks) and any single
On Thursday, 20 June 2013 at 14:37:51 UTC, Adam D. Ruppe wrote:
Is it just me or has Rust completely displaced Go as the go-to
'why D when we have X' thing on the reddit?
It seems like not even a full year ago, Rust was rarely
mentioned and all the versus hype was about Go. Will Rust fade
On Friday, 21 June 2013 at 11:13:49 UTC, Paulo Pinto wrote:
If you have powerful entities pushing a language down
developers throats, it will get used. That is how many
mainstream languages got where they are now.
It will be used if its capabilities suit target domain. In other
words, no
On Wednesday, 26 June 2013 at 11:08:17 UTC, Leandro Lucarella
wrote:
Android might be the only valid case (but I'm not really
familiar with Android model), but the kernel, since is based on
Linux, has to have the source code when
released. Maybe the drivers are closed source.
It is perfectly
Hm, bub.. Sounds like it should work with 'dub' nicely ;)
Looks promising and I'd really love to see some build tool other
then rdmd getting to the point it can be called standard.
Makefile's sometimes are just too inconvenient.
On Thursday, 27 June 2013 at 13:18:01 UTC, Joakim wrote:
There is no point talking to people who make blatantly ignorant
statements
Yeah, I keep wondering why someone even bothered to waste time
explaining all this to someone who is incapable of both providing
own reasoning and studying
On Friday, 28 June 2013 at 16:00:57 UTC, Andrej Mitrovic wrote:
Deimos is an overhead which provides no benefits. It was
supposed to
be used to make discovery easy, but discovery can be done
through a
wiki, or dlang.org, or an automated process (dub).
I suspect with time Deimos will be
On Tuesday, 2 July 2013 at 13:33:10 UTC, Michal Minich wrote:
Ok I understand. What I did as a first thing when I get error
on char[] x = a was char x = cast(char[])a, Which was
obviously incorrect - as the a was/should be placed in rom.
So if this expression is allays wrong - casting string
On Monday, 8 July 2013 at 17:53:45 UTC, Joseph Rushton Wakeling
wrote:
There'd need to be some way of filtering upstreams by topic. I
blog about D, but not _just_ about D.
http://planet.dsource.org has already been mentioned and it does
filter by tags.
On Tuesday, 9 July 2013 at 15:35:31 UTC, Andrei Alexandrescu
wrote:
I got permission. Videos can be uploaded to youtube as long as
NDC Oslo 2013 is mentioned.
Andrei
http://youtu.be/2W0G_FcSPcE
http://youtu.be/G5O_ypjlDD8
On Saturday, 27 July 2013 at 22:27:35 UTC, Brian Schott wrote:
DScanner is a tool for analyzing D source code. It has the
following features:
* Prints out a complete AST of a source file in XML format.
* Syntax checks code and prints warning/error messages
* Prints a listing of modules
On Sunday, 28 July 2013 at 13:44:03 UTC, Jacob Carlborg wrote:
I don't think it's necessary for semantic analysis to be
included in Phobos. It's enough to start with a lexer, then
later add a parser and semantic analysis.
Those were 2 separate not related questions ;)
On Tuesday, 30 July 2013 at 13:53:24 UTC, Chris wrote:
Dear Dees,
Here is the article. I've set up a (temporary?) blog for it.
The article deals with the usability of D and how it helped
to solve certain problems. It's not about benchmarking,
concurrency, unit tests and the like. Just about
On Sunday, 11 August 2013 at 17:15:52 UTC, David Nadlinger wrote:
What would be nice, however, is to have these D-specific tools
such as DVM, dub, … available in the distro repositories
Work in progress :)
On Monday, 12 August 2013 at 13:06:46 UTC, Mike Parker wrote:
As long as packaging the various distros doesn't require any
constraints on how I manage my projects, then it doesn't matter
too much to me where or how people package it up. However, I do
see benefits to promoting dub as the means
On Monday, 12 August 2013 at 13:46:52 UTC, David wrote:
LDC is in [community] already, and iirc Dicebot is working on
getting
GDC into [community], too
Actually I am simply waiting until my PGP key gets signed by at
least 3 Arch Linux master keys :) Will make announcement about
all package
On Monday, 12 August 2013 at 14:34:04 UTC, Mike Parker wrote:
That's true. But, correct me if I'm wrong, rpms and the like
are bundled independently of the original source repository. So
a project relying solely on dub doesn't stop a package
maintainer from keeping a separate build script to
On Monday, 12 August 2013 at 15:55:10 UTC, Mike Parker wrote:
My view may indeed be heavily tinted by Windows, where this
sort of thing just isn't an issue to care about. I suppose I'll
have to adjust that a bit.
Hah, yeah, I guess the very understanding of user-distributed
package is very
On Thursday, 15 August 2013 at 17:55:38 UTC, monarch_dodra wrote:
I'll chime in thanking Jonathan for this valuable contribution.
I think I'll chip in by answering questions on SO too. I enjoy
helping.
Be warned - by the time notification about new question arrives
in RSS feed, it usually
packages):
https://github.com/Dicebot/Arch-PKGBUILDs
Both accepting pull requests and checking for bug reports there.
--
Adding new D packages
--
https://wiki.archlinux.org
On Sunday, 25 August 2013 at 19:45:38 UTC, Johannes Pfau wrote:
Am Sun, 25 Aug 2013 21:11:51 +0200
schrieb Dicebot pub...@dicebot.lv:
Greetings to fellow Arch Linux users - quite a lot of stuff has
happened there recently in relation to D and this should sum it
up.
Some changes may have
On Sunday, 25 August 2013 at 20:33:49 UTC, Jordi Sayol wrote:
Is it not better:
- libphobos2.a
- liblphobos2.a
- libgphobos2.a
It is libphobos2.a, of course, typo-paste :)
Is it not better:
- libphobos2.so
Same here (blush)
What's the Arch Linux way to name
On Sunday, 25 August 2013 at 23:17:22 UTC, Andrei Alexandrescu
wrote:
On 8/25/13 12:11 PM, Dicebot wrote:
Greetings to fellow Arch Linux users - quite a lot of stuff has
happened there recently in relation to D and this should sum it
up.
Some changes may have not been synchronised to all
On Sunday, 25 August 2013 at 22:35:50 UTC, John Colvin wrote:
OT:
This might be the final straw that takes me over to Arch.
How are things over on that side of linux? I've been using
ubuntu/lubuntu/fedora/mint on various machines for years but
never really tried out the more DIY distros.
I
On Monday, 26 August 2013 at 06:55:50 UTC, Jacob Carlborg wrote:
I was about to tag dstep for a new release but I wanted to make
a proper release as well, providing pre-compiled binaries and
so on. Unfortunately I haven't been able to produce a working
binary on Linux 32bit, which is weird
On Monday, 26 August 2013 at 10:52:23 UTC, Mike Wey wrote:
Usually the actual binary has the fully qualified version
number, and libphobos2.so would be included/created by the
devel package.
Yes, that does seem to be the case with other packages, I am
simply reluctant to make any steps
1 - 100 of 550 matches
Mail list logo