Benjamin Thaut wrote:
I rewrote a 3d game I created during my studies with D 2.0 to manual
memory mangement. If I'm not studying I'm working in the 3d Engine
deparement of Havok. As I needed to pratice manual memory management
and did want to get rid of the GC in D for quite some time, I did
Hi,
it's my pleasure to announce the begin of the formal review of Andrei's
std.benchmark. The review will start today and end in two weeks, on 1st
of October. The review is followed by a week of voting which ends on 8th
of October.
Quoting Andrei from his request for formal review:
I reworked
Walter Bright wrote:
References:
http://www.digitalmars.com/d/archives/digitalmars/D/Custom_attributes_again_163042.html
http://www.digitalmars.com/d/archives/digitalmars/D/custom_attribute_proposal_yeah_another_one_163246.html
Inspired by a gallon of coffee, I decided to get it
Jens Mueller wrote:
Walter Bright wrote:
References:
http://www.digitalmars.com/d/archives/digitalmars/D/Custom_attributes_again_163042.html
http://www.digitalmars.com/d/archives/digitalmars/D/custom_attribute_proposal_yeah_another_one_163246.html
Inspired by a gallon of coffee
Moritz Maxeiner wrote:
Hi, I would like to announce llvm-d, which provides LLVM bindings
for D.
It loads LLVM from a dynamic library (so/dylib/dll) and has support
for LLVM versions 3.1, 3.2 and 3.3 (current svn trunk).
It has as of now been tested on 64bit versions of Archlinux, OS X
Moritz Maxeiner wrote:
On Friday, 15 March 2013 at 21:18:09 UTC, Jens Mueller wrote:
Nice.
Can you make it compatible with Deimos
https://github.com/D-Programming-Deimos/?
Jens
If by compatible you mean can be used with:
I don't see anything that would prevent you from using llvm-d
Moritz Maxeiner wrote:
On Sunday, 17 March 2013 at 20:05:09 UTC, Jens Mueller wrote:
Deimos just provides a plain D interface for C libraries.
What do you mean?
You can do static or dynamic linking.
With dynamic linking it will be loaded at startup time by the
loader.
But you can also load
Moritz Maxeiner wrote:
On Monday, 18 March 2013 at 13:50:29 UTC, Jens Mueller wrote:
I don't know how this is done on Windows. On Linux you just set
the
LD_LIBRARY_PATH.
My problem with that is that it's a) not encapsulated inside the
program and b) OS dependent.
Very true. Do you have
Moritz Maxeiner wrote:
On Monday, 18 March 2013 at 14:51:00 UTC, Jens Mueller wrote:
Moritz Maxeiner wrote:
On Monday, 18 March 2013 at 13:50:29 UTC, Jens Mueller wrote:
I'll to that, then. I'm currently working on the D API, but I'll
try
to get the copied deimos compatible project started
Jens Mueller wrote:
Moritz Maxeiner wrote:
On Monday, 18 March 2013 at 14:51:00 UTC, Jens Mueller wrote:
Moritz Maxeiner wrote:
On Monday, 18 March 2013 at 13:50:29 UTC, Jens Mueller wrote:
I'll to that, then. I'm currently working on the D API, but I'll
try
to get the copied
Moritz Maxeiner wrote:
On Friday, 22 March 2013 at 08:34:11 UTC, Jens Mueller wrote:
Updated documentation
http://jkm.github.com/d-programming-language.org/deimos.html
NIice, but conforming to the following would create too much work
for me:
For each file a proper module declaration has
Moritz Maxeiner wrote:
On Friday, 22 March 2013 at 17:16:26 UTC, Jens Mueller wrote:
Moritz Maxeiner wrote:
On Friday, 22 March 2013 at 08:34:11 UTC, Jens Mueller wrote:
Updated documentation
http://jkm.github.com/d-programming-language.org/deimos.html
NIice, but conforming
Moritz Maxeiner wrote:
On Saturday, 23 March 2013 at 09:30:07 UTC, Jens Mueller wrote:
Moritz Maxeiner wrote:
A couple of more things I forgot to mention:
- You will need to additionally add bindings for all the
LLVMInitializeTARGET_NAME{TargetInfo,Target,TargetMC,AsmParser,AsmPrinter
Moritz Maxeiner wrote:
On Saturday, 23 March 2013 at 10:31:30 UTC, Jens Mueller wrote:
Moritz Maxeiner wrote:
On Saturday, 23 March 2013 at 09:30:07 UTC, Jens Mueller wrote:
Moritz Maxeiner wrote:
A couple of more things I forgot to mention:
- You will need to additionally add bindings
Moritz Maxeiner wrote:
On Saturday, 23 March 2013 at 16:37:35 UTC, Jens Mueller wrote:
Moritz Maxeiner wrote:
On Saturday, 23 March 2013 at 10:31:30 UTC, Jens Mueller wrote:
It looks mostly okay to me with one problem: Afaict the code
enforces the presence of the initialization routines
Moritz Maxeiner wrote:
On Saturday, 23 March 2013 at 21:24:50 UTC, Jens Mueller wrote:
Moritz Maxeiner wrote:
On Saturday, 23 March 2013 at 16:37:35 UTC, Jens Mueller wrote:
Moritz Maxeiner wrote:
On Saturday, 23 March 2013 at 10:31:30 UTC, Jens Mueller
wrote:
It looks mostly okay to me
deadalnix wrote:
I think passing the path -J should work. But I don't know what to
do
when there is no Targets.def.
Jens
Off topic, but can you please ensure not to split the thread like
this ?
How do I ensure this?
I'm using the mailman interface.
There are no such problems with
Mike Wey wrote:
On 07/27/2012 09:33 AM, Alex Rønne Petersen wrote:
On 27-07-2012 09:31, Jens Mueller wrote:
Alex Rønne Petersen wrote:
On 27-07-2012 07:23, Jens Mueller wrote:
Hi,
I've read several threads that about creating shared libraries. But I
could not make it work.
Does anybody
Nick Sabalausky wrote:
On Fri, 17 Aug 2012 00:20:10 +0200
TJB broug...@gmail.com wrote:
D Masters,
I'm not a hardware guy at all, but I find myself needing to
process a lot of data through some Monte Carlo statistical
algorithms. I am considering general purpose GPU computing for
Dmitry Olshansky wrote:
The discussion around new unified API for digest hash functions has
subdued, just in time as the review period has ended.
The voting for std.digest package starts today and ends on 29
August.
Rules are simple: reply in this thread with definite YES or NO
on
d_follower wrote:
On Wednesday, 22 August 2012 at 12:36:08 UTC, Dmitry Olshansky
wrote:
The discussion around new unified API for digest hash functions
has subdued, just in time as the review period has ended.
The voting for std.digest package starts today and ends on 29
August.
Rules
Johannes Pfau wrote:
Am Thu, 23 Aug 2012 22:46:35 +0200
schrieb Jens Mueller jens.k.muel...@gmx.de:
It says Digests do not work in CTFE.
Just checked it for MD5.
I do not know but I think this is just a current limitation of the
CTFE implementation.
It's possible to support CTFE
Jonathan M Davis wrote:
On Saturday, August 25, 2012 21:58:12 timotheecour wrote:
is that a bug? should i file a bug report?
I'd have to study it more to say, but std.algorithm doesn't play very nicely
with const right now. More work needs to be done in that area, and stuff like
Jonathan M Davis wrote:
On Sunday, August 26, 2012 14:47:38 Jens Mueller wrote:
What is the ref situation?
I thought ref is used as an optimization that allows passing lvalues
more efficiently whereas without ref is needed for rvalues.
ref doesn't necessarily have anything to do
Andrei Alexandrescu wrote:
On 9/6/12 9:22 AM, Jacob Carlborg wrote:
On 2012-09-06 02:30, jerro wrote:
reason to do with not finding druntime.
You probably didn't do
git submodule init; git submodule update
Or in one command:
$ git submodule update --init
You can also add
Andrei Alexandrescu wrote:
On 9/6/12 9:22 AM, Jacob Carlborg wrote:
On 2012-09-06 02:30, jerro wrote:
reason to do with not finding druntime.
You probably didn't do
git submodule init; git submodule update
Or in one command:
$ git submodule update --init
You can also add
Andrei Alexandrescu wrote:
On 9/6/12 11:57 AM, Jens Mueller wrote:
BTW I've added pointers for the LDC instructions to the download
page: http://dlang.org/download.html. Feedback welcome.
I think you forgot to add the Gentoo logo to git.
Jens
You're right, thanks! Done now.
Link
Andrei Alexandrescu wrote:
I recall we have nothing in the review queue for the time being, is
that correct?
If that's the case, allow me to tender std.benchmark again for
inclusion into Phobos. I reworked the benchmarking framework for
backward compatibility, flexibility, and convenience.
Hi,
it's my pleasure to announce the begin of the formal review of Andrei's
std.benchmark. The review will start today and end in two weeks, on 1st
of October. The review is followed by a week of voting which ends on 8th
of October.
Quoting Andrei from his request for formal review:
I reworked
Daniel wrote:
I have searched everywhere and I can't find anything so I decided to
come here. I have a simple Hello World program in the file Test.d,
it compiles just fine but when I try this...
Can you attach the Test.d?
But it looks like you didn't define a main function.
[daniel@arch D]$
Johannes Pfau wrote:
Current situation:
The compiler combines all unittests of a module into one huge function.
If a unittest in a module fails, the rest won't be executed. The
runtime (which is responsible for calling that per module unittest
method) must always run all unittests of a
Jonathan M Davis wrote:
On Thursday, September 20, 2012 18:53:38 Johannes Pfau wrote:
Proposal:
[snip]
In general, I'm all for instrumenting druntime such that unit testing tools
could run unit tests individually and present their output in a customized
manner, just so long as it
Hi,
I do not understand the following error message given the code:
string foo(string f)
{
if (f == somestring)
{
return got somestring;
}
return bar!(foo(somestring));
}
template bar(string s)
{
enum bar = s;
}
I'll with dmd v2.060 get:
test.d(7):called
Jonathan M Davis wrote:
On Thursday, September 20, 2012 22:55:23 Jens Mueller wrote:
You say that JUnit silently runs all unittests before the first
specified one, don't you?
Yes. At least, that was its behavior the last time that I used it (which was
admittedly a few years ago
Simen Kjaeraas wrote:
On Thu, 20 Sep 2012 23:22:36 +0200, Jens Mueller
jens.k.muel...@gmx.de wrote:
string foo(string f)
{
if (f == somestring)
{
return got somestring;
}
return bar!(foo(somestring));
}
template bar(string s)
{
enum bar = s
Jonathan M Davis wrote:
On Thursday, September 20, 2012 23:22:36 Jens Mueller wrote:
Hi,
I do not understand the following error message given the code:
string foo(string f)
{
if (f == somestring)
{
return got somestring;
}
return bar!(foo(somestring));
}
template
Jonathan M Davis wrote:
On Friday, September 21, 2012 00:11:51 Jens Mueller wrote:
I thought foo is interpreted at compile time.
There seems to be a subtle difference I'm not getting.
Because you can do the factorial using CTFE even though you have
recursion. I.e. there you have a call
Andrei Alexandrescu wrote:
I've met Matt Goldbolt, the author of the GCC Explorer at
http://gcc.godbolt.org - a very handy online disassembler for GCC.
This is not a disassembler. It just stops compilation before the
assembler (gcc -S). A dissembler would create the assembler code given
only
Jens Mueller wrote:
Jonathan M Davis wrote:
On Friday, September 21, 2012 00:11:51 Jens Mueller wrote:
I thought foo is interpreted at compile time.
There seems to be a subtle difference I'm not getting.
Because you can do the factorial using CTFE even though you have
recursion. I.e
Timon Gehr wrote:
On 09/20/2012 11:22 PM, Jens Mueller wrote:
Hi,
I do not understand the following error message given the code:
string foo(string f)
{
if (f == somestring)
{
return got somestring;
}
return bar!(foo(somestring));
}
template bar
Iain Buclaw wrote:
On 21 September 2012 11:29, Iain Buclaw ibuc...@ubuntu.com wrote:
On 21 September 2012 11:17, Bernard Helyer b.hel...@gmail.com wrote:
On Friday, 21 September 2012 at 10:04:00 UTC, Jens Mueller wrote:
Andrei Alexandrescu wrote:
I've met Matt Goldbolt, the author
Johannes Pfau wrote:
Am Fri, 21 Sep 2012 11:11:49 +0200
schrieb Jacob Carlborg d...@me.com:
On 2012-09-20 21:11, Johannes Pfau wrote:
Oh right, I thought that interface was more restrictive. So the only
changes necessary in druntime are to adapt to the new compiler
interface.
Jacob Carlborg wrote:
On 2012-09-21 14:19, Jens Mueller wrote:
Why do you need filename and line information of a unittest. If a
unittest fails you'll get the relevant information. Why do you want the
information when a unittest succeeded? I only care about failed
unittests. A count
Johannes Pfau wrote:
Am Fri, 21 Sep 2012 16:37:37 +0200
schrieb Jens Mueller jens.k.muel...@gmx.de:
Jacob Carlborg wrote:
On 2012-09-21 14:19, Jens Mueller wrote:
Why do you need filename and line information of a unittest. If a
unittest fails you'll get the relevant information
Jacob Carlborg wrote:
On 2012-09-21 16:37, Jens Mueller wrote:
If there are use cases I agree. I do not know one.
The question whether there are *tools* that report in case of success is
easier to verify. Do you know any tool that does reporting in case
success? I think gtest does not do
Tobias Pankrath wrote:
I'm actually kinda surprised the feedback on this is rather
negative. I
thought running unit tests individually and printing
line/file/name was
requested quite often?
I want to have this. My workflow is: Run all tests0(run all). If
some fail, see if there might be
Jacob Carlborg wrote:
On 2012-09-21 20:01, Johannes Pfau wrote:
I didn't think of setAssertHandler. My changes are perfectly compatible
with it.
IIRC setAssertHandler has the small downside that it's used for all
asserts, not only those used in unit tests? I'm not sure if that's a
drawback
David Piepgrass wrote:
However, what's truly insane IMHO is continuing to run a unittest
block after
it's already had a failure in it. Unless you have exceedingly
simplistic unit
tests, the failures after the first one mean pretty much _nothing_
and simply
clutter the results.
I
Ellery Newcomer wrote:
On 09/21/2012 03:04 AM, Jens Mueller wrote:
But it's nice to have source code and assembly side by side.
Jens
And very nice to have demangled names in assembly.
You can pipe your assembly code to ddemangle if there is some other tool
that missing demangling. I did
Andrei Alexandrescu wrote:
On 9/21/12 5:39 AM, Jacob Carlborg wrote:
On 2012-09-21 06:23, Andrei Alexandrescu wrote:
For a very simple reason: unless the algorithm under benchmark is very
long-running, max is completely useless, and it ruins average as well.
I may have completely
Jacob Carlborg wrote:
On 2012-09-21 23:11, Jens Mueller wrote:
But if you have an assert in some algorithm to ensure some invariant or
in a contract it will be handled by myUnitTestSpecificAssertHandler.
But I think that is not a drawback. Don't you want to no whenever an
assert is violated
Johannes Pfau wrote:
Am Fri, 21 Sep 2012 23:15:33 +0200
schrieb Jens Mueller jens.k.muel...@gmx.de:
I like the BOOST unit test library's approach, which has two types
of assert: BOOST_CHECK and BOOST_REQUIRE. After a BOOST_CHECK
fails, the test keeps running, but BOOST_REQUIRE throws
Jacob Carlborg wrote:
On 2012-09-22 19:43, Jens Mueller wrote:
What does it mean to make no distinction in RSpec?
Both should be reported. In D you just see either an AssertError or
SomeException.
Test-unit would report something like this:
5 tests, 2 failures, 1 error
Failures
Maxim Fomin wrote:
You can build shared libraries on linux by manually compiling object
files and linking them. On windows last time I tries it was not
possible.
Can you give detailed steps for doing this on Linux? Because nobody as
far as I know has made this work yet?
Jens
Jacob Carlborg wrote:
On 2012-09-27 10:04, Maxim Fomin wrote:
On Thursday, 27 September 2012 at 05:52:44 UTC, Jens Mueller
wrote:
Maxim Fomin wrote:
You can build shared libraries on linux by manually compiling object
files and linking them. On windows last time I tries it was not
possible
Jens Mueller wrote:
Hi,
it's my pleasure to announce the begin of the formal review of Andrei's
std.benchmark. The review will start today and end in two weeks, on 1st
of October. The review is followed by a week of voting which ends on 8th
of October.
Quoting Andrei from his request
Andrei Alexandrescu wrote:
On 10/1/12 9:09 PM, Jens Mueller wrote:
The review of std.benchmark is over.
I'd like to give some conclusions regarding the review of the proposed
benchmarking module hoping to reach some consensus on how to proceed.
[snip]
Thanks Jens for shepherding the review
mist wrote:
After some gentle preachings I have been asked in my company to
prepare presentation regarding D usage in scope of embedded,
kernel-level development and mobile devices. I am quite starving to
find good project examples for D2 though ( most stuff I am aware of
is D1 ) and do not
Jonathan M Davis wrote:
On Tuesday, October 16, 2012 10:58:23 David Gileadi wrote:
On 10/16/12 10:28 AM, Jonathan M Davis wrote:
Any range is free to violate this, but because range-based functions are
free to rely on it, such ranges risk not working correctly with many
range-based
Robik wrote:
Hello,
I would like to introduce ColorD, small library that allows to
simply manipulate console output colors, both on Windows and Posix
operating systems. It also supports font styles such as underline
and strikethrough(Posix feature only).
Simple example:
import
Robik wrote:
On Sunday, 21 October 2012 at 21:01:21 UTC, Jens Mueller wrote:
Interesting looks solid to me.
Some nit-picks:
* Coloring on Posix depends a ANSI terminal. Can you check that a
terminal is ANSI compatible?
Sure, why not.
Do you know how to do this?
* There are some magic
Era Scarecrow wrote:
On Sunday, 21 October 2012 at 19:28:21 UTC, Robik wrote:
I would like to introduce ColorD, small library that allows to
simply manipulate console output colors, both on Windows and Posix
operating systems. It also supports font styles such as underline
and
Chad J wrote:
On 10/21/2012 05:01 PM, Jens Mueller wrote:
Robik wrote:
Hello,
I would like to introduce ColorD, small library that allows to
simply manipulate console output colors, both on Windows and Posix
operating systems. It also supports font styles such as underline
Chad J wrote:
On 10/21/2012 06:11 PM, Jens Mueller wrote:
Chad J wrote:
On 10/21/2012 05:01 PM, Jens Mueller wrote:
It seems to have a hard ncurses/termcap/etc dependency.
Yes. I think you cannot make it portable without. Please proof me wrong
and I'll fix this.
Well, traditionally
Walter Bright wrote:
On 10/21/2012 12:28 PM, Robik wrote:
Simple example:
import std.stdio, colord;
void main()
{
setConsoleColors(Fg.red, Bg.blue);
writeln(Red text on blue background.);
resetConsoleColors(); // Bring back initial state
}
Need a method to get
Chad J wrote:
On 10/21/2012 06:55 PM, Jens Mueller wrote:
Chad J wrote:
On 10/21/2012 06:11 PM, Jens Mueller wrote:
Chad J wrote:
On 10/21/2012 05:01 PM, Jens Mueller wrote:
It seems to have a hard ncurses/termcap/etc dependency.
Yes. I think you cannot make it portable without. Please
Andrei Alexandrescu wrote:
On 10/22/12 9:47 AM, Jens Mueller wrote:
This is probably interesting for Phobos. But I'm not the one to make a
decision. The core Phobos developers should decide.
Hopefully somebody is reading this.
Off the top of my head something that is specific for only
Robik wrote:
On Sunday, 21 October 2012 at 22:32:35 UTC, Walter Bright wrote:
On 10/21/2012 12:28 PM, Robik wrote:
Simple example:
import std.stdio, colord;
void main()
{
setConsoleColors(Fg.red, Bg.blue);
writeln(Red text on blue background.);
Andrei Alexandrescu wrote:
On 10/22/12 8:24 AM, Jens Mueller wrote:
Andrei Alexandrescu wrote:
On 10/22/12 9:47 AM, Jens Mueller wrote:
This is probably interesting for Phobos. But I'm not the one to make a
decision. The core Phobos developers should decide.
Hopefully somebody is reading
Chad J wrote:
On 10/22/2012 03:47 AM, Jens Mueller wrote:
Chad J wrote:
There is no weakness to this. The only shred of a counterargument I
can think of is that it makes the format strings more difficult to
learn. Other than that, it is possible to detect the destination of
the formatter
Chad J wrote:
On 10/23/2012 03:51 AM, Jens Mueller wrote:
Chad J wrote:
On 10/22/2012 03:47 AM, Jens Mueller wrote:
Chad J wrote:
There is no weakness to this. The only shred of a counterargument I
can think of is that it makes the format strings more difficult to
learn. Other than
Jens Mueller wrote:
Chad J wrote:
On 10/23/2012 03:51 AM, Jens Mueller wrote:
Chad J wrote:
On 10/22/2012 03:47 AM, Jens Mueller wrote:
Chad J wrote:
There is no weakness to this. The only shred of a counterargument I
can think of is that it makes the format strings more difficult
Chad J wrote:
On 10/23/2012 04:42 PM, Jens Mueller wrote:
Jens Mueller wrote:
Chad J wrote:
That's a reasonable suggestion. The only thing that can't be solved
is the trailing ) enclosing the text to be formatted. That needs a
% before it to prevent ambiguity with parentheses in the text
Robert wrote:
When reading stuff, like: Yes this is bad, but people use it already,
so we could only possible change this in D3 or something and reading
endless discussions about a new feature (e.g. ref semantics) of how it
could break things and so on, I thought it might be a good idea to
Robert Klotzner wrote:
Simply don't release a new stable version with new features, semantics,
but first release an experimental version. Encourage people to compile
their code with it, try out the new features/semantics, ... but always
let them keep in mind, that things can break with further
Mike van Dongen wrote:
Hi all!
I've been working on an URI parser which takes a string and then
separates the parts and puts them in the correct properties.
If a valid URI was provided, the (static) parser will return an
instance of Uri.
I've commented all relevant lines of code and
Jonathan M Davis wrote:
On Thursday, October 25, 2012 15:59:39 Jens Mueller wrote:
* Should URIs be only movable? Then you should add
@disable this(this);
I'd be shocked if that were appropriate. Disabling the init property like
that
should be done extremely rarely and only if you need
Jacob Carlborg wrote:
On 2012-10-25 15:20, Mike van Dongen wrote:
It's a dirty job, but someone's gotta do it ;)
I have commented all code that's not straightforward, but nothing for
the Ddoc.
If think the ddoc is the most important one.
Can you give me an example of how specific I
Mike van Dongen wrote:
On Thursday, 25 October 2012 at 13:59:59 UTC, Jens Mueller wrote:
Just some small nit-picks.
That's what I was hoping for :D
in general checkout the Phobos style guide regarding function
names
etc.
http://dlang.org/dstyle.html
add some unittests
Jacob Carlborg wrote:
I've recently got some experience of a project called Travis CI. As
the title says it's a CI, Continuous Integration testing server for
open source projects. They host all the building and testing, you
just add a YAML configuration file and a github hook and then it can
Jonathan M Davis wrote:
On Thursday, October 25, 2012 23:05:14 Jens Mueller wrote:
Jonathan M Davis wrote:
On Thursday, October 25, 2012 15:59:39 Jens Mueller wrote:
* Should URIs be only movable? Then you should add
@disable this(this);
I'd be shocked if that were appropriate
Walter Bright wrote:
On 10/22/2012 3:55 AM, Andrei Alexandrescu wrote: On 10/22/12 9:47
AM, Jens Mueller wrote:
This is probably interesting for Phobos. But I'm not the one to make a
decision. The core Phobos developers should decide.
Hopefully somebody is reading this.
Off the top
H. S. Teoh wrote:
On Fri, Oct 26, 2012 at 12:27:38AM +0200, Jens Mueller wrote:
Walter Bright wrote:
[...]
A module that only sets the console color is a little too light to
be a phobos entry.
A more comprehensive module that included:
1. getting mouse input
Anybody
Adam D. Ruppe wrote:
On Thursday, 25 October 2012 at 22:27:52 UTC, Jens Mueller wrote:
5. setting the contents of the title bar
The title bar of what?
Here's how you do it on xterm:
writefln(\033]0;%s\007, title);
On Windows it is an api function:
http://msdn.microsoft.com/en-us
Jacob Carlborg wrote:
On 2012-10-25 23:06, Jens Mueller wrote:
I'd prefer the second option. Maybe write first some unittests for
std.uri, if there are none. Then move it.
Agree, but we want to minimize the code breakage.
That's what the unittests are for.
Code breakage that results
Jacob Carlborg wrote:
On 2012-10-25 23:47, Jens Mueller wrote:
I've been using cloudbees.com which offers a similar service based on
Jenkins.
Since Jenkins supports shell scripts to drive the build it was fairly
easy to support D (see https://gluey.ci.cloudbees.com/job/ddl/).
Travis
H. S. Teoh wrote:
Is it just me, or has dlang.org been really slow today? Is something
wrong with the site that needs our attention? It takes almost 2 whole
minutes to load a page -- at first I thought my office network screwed
up again, but now I'm at home and it's still like that.
Same
Jonathan M Davis wrote:
On Friday, October 26, 2012 10:11:04 Jens Mueller wrote:
Jacob Carlborg wrote:
On 2012-10-25 23:06, Jens Mueller wrote:
I'd prefer the second option. Maybe write first some unittests for
std.uri, if there are none. Then move it.
Agree, but we want
Jonathan M Davis wrote:
On Friday, October 26, 2012 10:59:17 Jens Mueller wrote:
No. The issue is code breakage in the code of people using Phobos, and if
you change where the module is, you'll break code. Even if we provide a
deprecation path from std.uri to std.net.uri, that still
Jonathan M Davis wrote:
On Friday, October 26, 2012 11:27:40 Jens Mueller wrote:
Is it okay to have both modules and only state in std.uri's
documentation that you shouldn't use it anymore (similar to std.xml)?
This would break no code.
If we were to move it, we'd temporarily leave
Jacob Carlborg wrote:
On 2012-10-26 11:53, Jens Mueller wrote:
Unfortunately there are no portable solutions. The only thing I found is
symbol versioning. But this is only supported by GNU ld.
These strategic issues need to be solved.
There are many other solutions that can be used
H. S. Teoh wrote:
On Fri, Oct 26, 2012 at 08:08:36AM +0200, Robik wrote:
On Friday, 26 October 2012 at 01:35:43 UTC, Adam D. Ruppe wrote:
On Thursday, 25 October 2012 at 22:27:52 UTC, Jens Mueller wrote:
5. setting the contents of the title bar
The title bar of what?
Here's how you
Jonathan M Davis wrote:
On Friday, October 26, 2012 19:46:16 deadalnix wrote:
Le 25/10/2012 04:12, Jonathan M Davis a écrit :
On Wednesday, October 24, 2012 13:31:14 Walter Bright wrote:
The default compare for structs is a bit compare of the contents.
Which definitely seems
Walter Bright wrote:
On 10/26/2012 2:13 AM, Jonathan M Davis wrote: There's definitely
some truth to that, but Walter in particular seems to be
against breaking anything period.
We have a number of fed up developers and abandoned, dead projects
because of breaking changes.
It MUST STOP.
Adam D. Ruppe wrote:
Here we go, some more basic functions:
http://arsdnet.net/dcode/terminal.d
The unix stuff is more implemented than the windows.
Let's walk through main and I'll discuss why I'm doing things the
way I am. I'm throwing this out just to show one possible way this
Tobias Pankrath wrote:
On Tuesday, 23 October 2012 at 22:47:40 UTC, Walter Bright wrote:
On 10/22/2012 3:55 AM, Andrei Alexandrescu wrote: On 10/22/12
9:47 AM, Jens Mueller wrote:
This is probably interesting for Phobos. But I'm not the one
to make a
decision. The core Phobos developers
Adam D. Ruppe wrote:
It now can translate most PC keyboard input sequences into char or
non-char key events, including requesting UTF-8 input for chars:
http://arsdnet.net/dcode/terminal.d
We could just about start writing real apps with this now. Biggest
problem left is it doesn't
Adam D. Ruppe wrote:
On Sunday, 28 October 2012 at 10:44:58 UTC, Jens Mueller wrote:
How?
The file /etc/termcap has the data too so opening it and quickly
parsing should give the same result as the environment variable.
I'm running Debian. It doesn't have such a file.
It looks like
Jonathan M Davis wrote:
On Monday, October 29, 2012 20:26:38 Dmitry Olshansky wrote:
Need to ping Jonathon about it and work out something.
I believe that Microsoft did something stupid with one of their functions
which makes it function slightly differently around a DST switch on Windows
Jacob Carlborg wrote:
On 2012-11-01 23:51, Walter Bright wrote:
What about all your feature requests? I think you've made more than
anyone, by a factor of 10 at least!
:-)
As for Manu's request
http://d.puremagic.com/issues/show_bug.cgi?id=8108
I've gone over with him why he needs
1 - 100 of 441 matches
Mail list logo
