Am 02.01.2014 21:14, schrieb Daniel Kozak:
F***ing captcha F***ing captcha F***ing captcha F***ing captcha F***ing
captcha F***ing captcha F***ing captcha F***ing captcha F***ing captcha
F***ing captcha F***ing captcha F***ing captcha F***ing captcha F***ing
captcha F***ing captcha F***ing captch
On Thursday, 2 January 2014 at 20:14:58 UTC, Daniel Kozak wrote:
F***ing captcha F***ing captcha F***ing captcha F***ing captcha
F***ing captcha F***ing captcha F***ing captcha F***ing captcha
F***ing captcha F***ing captcha F***ing captcha F***ing captcha
F***ing captcha F***ing captcha F***in
Thanks, maybe I was too tired and do not read carefully the captcha ;-).
Dne Fri, 03 Jan 2014 10:19:43 +0100 Vladimir Panteleev
napsal(a):
On Thursday, 2 January 2014 at 20:14:58 UTC, Daniel Kozak wrote:
F***ing captcha F***ing captcha F***ing captcha F***ing captcha F***ing
captcha F***
On Thursday, 2 January 2014 at 14:49:50 UTC, Ola Fosheim Grøstad
wrote:
I like the nice little compiler app on the frontpage, but it
gets killed most of the time leaving an error. Which is kind of
unfortunate.
Thank you for reporting this!
Looks like something got borked on dlang.org side.
The
On Friday, 3 January 2014 at 03:59:50 UTC, Jonathan M Davis wrote:
On Friday, January 03, 2014 03:13:12 alex burton wrote:
struct Foo
{
};
void bar(ref Foo f)
{
}
void main()
{
bar(Foo()); //Error: function test.bar (ref Foo f) is not
callable using argument types (Foo)
}
I get the above erro
On Friday, January 03, 2014 10:06:49 alex burton wrote:
> On Friday, 3 January 2014 at 03:59:50 UTC, Jonathan M Davis wrote:
> > On Friday, January 03, 2014 03:13:12 alex burton wrote:
> >> struct Foo
> >> {
> >> };
> >>
> >> void bar(ref Foo f)
> >> {
> >> }
> >>
> >> void main()
> >> {
> >> bar
On 2014-01-02 22:38, H. S. Teoh wrote:
The limitation of macro systems is that, fundamentally speaking, no
semantics are assigned to macros. A macro is just an arbitrary name that
gets recursively substituted with some pre-specified pattern. The macro
engine doesn't know what any of the macros
On 2014-01-03 01:56, Jonathan M Davis wrote:
That depends on how you go about post-processing. If you design your ddoc
macros with the idea that there's going to be post-processing, then they can
convert to other ddoc macros which are designed for the post-processor to be
able to handle, and the
On 02.01.2014 12:35, Iain Buclaw wrote:
Special symbols can be suffixed with a $ perhaps. I can't think of
any other symbol that would work.
__init -> init$
__Class -> classinfo$
__vtbl -> vtable$
__interface -> interfaceinfo$
__ModuleInfo -> moduleinfo$
The alternative is to just go for p
On Friday, 3 January 2014 at 09:35:54 UTC, Daniel Kozák wrote:
Thanks, maybe I was too tired and do not read carefully the
captcha ;-).
Dne Fri, 03 Jan 2014 10:19:43 +0100 Vladimir Panteleev
napsal(a):
On Thursday, 2 January 2014 at 20:14:58 UTC, Daniel Kozak
wrote:
F***ing captcha F***i
On Friday, January 03, 2014 12:12:44 Jacob Carlborg wrote:
> On 2014-01-03 01:56, Jonathan M Davis wrote:
> > That depends on how you go about post-processing. If you design your ddoc
> > macros with the idea that there's going to be post-processing, then they
> > can convert to other ddoc macros w
XSLT is pretty useful for format conversion. It is also built
into most browsers, so you can just emit XML attach a XSLT
stylesheet and send it to a browser for transformation and
rendering.
Would be an advantage for anyone writing a book or article on D
(transform XML over to docbook, and fr
On 2014-01-03 04:14, alex burton wrote:
Also: I couldn't find how to download old versions to make a better
report on the version it was introduced in.
Links to old versions in the changelog point to the current version
download.
DVM is a great tool for installing older versions of DMD. I just
On 03/01/2014 00:03, Joseph Rushton Wakeling wrote:
On 03/01/14 00:33, Stewart Gordon wrote:
Please be specific.
You know, I'm starting to find your tone irritating. You are the one
who's asking for functionality that goes beyond any Complex
implementation that I'm aware of in any other langu
Here's the patch against GDB for anyone who wants to review.
https://github.com/ibuclaw/gdb/commit/6c187f7250c21a1b3ba2a09942b52ad238397d43
If no one sees anything that seems wrong, I'll submit this to GDB
this afternoon for inclusion.
Regards
Iain.
On 3 January 2014 14:26, Iain Buclaw wrote:
> Here's the patch against GDB for anyone who wants to review.
>
> https://github.com/ibuclaw/gdb/commit/6c187f7250c21a1b3ba2a09942b52ad238397d43
>
> If no one sees anything that seems wrong, I'll submit this to GDB this
> afternoon for inclusion.
>
Of
On 03/01/14 14:32, Stewart Gordon wrote:
I wasn't asking for it to go beyond the existing complex implementation or any
other. I was proposing that the arbitrary restriction be removed so that the
implementation we already have would work on them.
Yes, but it isn't an arbitrary restriction. T
On 9/3/13, Jacob Carlborg wrote:
> Could we get some form of API to set a header and footer that is printed
> with the help text. Possible idea:
>
> bool help;
>
> getopt(args, "h|help", &help, @doc("Show this message and exit.");
> getopt.header = "Usage foo [options]\nVersion 0.0.1\n\n";
> getop
please make this happen.
maybe a user defined help printing function would be useful. I could
image that printing the help information is something somebody would
like to modify.
On 01/03/2014 06:16 PM, Andrej Mitrovic wrote:
> On 9/3/13, Jacob Carlborg wrote:
>> Could we get some form of API to
On 03/01/2014 17:04, Joseph Rushton Wakeling wrote:
On 03/01/14 14:32, Stewart Gordon wrote:
I wasn't asking for it to go beyond the existing complex
implementation or any other. I was proposing that the arbitrary
restriction be removed so that the implementation we already have
would work on th
On 03/01/14 21:21, Stewart Gordon wrote:
How can isFloatLike be implemented?
I'm not sure. It's something that needs to be thought about and of course it
also depends on whether you want it to test just for basic properties, or
whether it is supported by mathematical operations (sin, cos, ab
On Friday, January 03, 2014 14:26:07 Iain Buclaw wrote:
> Here's the patch against GDB for anyone who wants to review.
>
> https://github.com/ibuclaw/gdb/commit/6c187f7250c21a1b3ba2a09942b52ad238397d
> 43
>
> If no one sees anything that seems wrong, I'll submit this to GDB
> this afternoon for i
I've run into a design issue surrounding ranges and am looking for advice
on the best way to proceed. To illustrate the issue, consider the
Shapefile format: a 100 byte header followed by variable-length records.
The tricky bit is that the header includes a field which contains the
total leng
On 3 January 2014 22:35, Jonathan M Davis wrote:
> On Friday, January 03, 2014 14:26:07 Iain Buclaw wrote:
>> Here's the patch against GDB for anyone who wants to review.
>>
>> https://github.com/ibuclaw/gdb/commit/6c187f7250c21a1b3ba2a09942b52ad238397d
>> 43
>>
>> If no one sees anything that see
"Chris Cain" writes:
> On Monday, 30 December 2013 at 11:23:22 UTC, JN wrote:
>> The best you can do in those
>> languages usually is to just not allocate stuff during the game.
>
> Yeah. The techniques to accomplish this in GC-only languages surprisingly
> mirror some of the techniques where mal
On Friday, 3 January 2014 at 22:56:41 UTC, Justin Whear wrote:
I've run into a design issue surrounding ranges and am looking
for advice
on the best way to proceed. To illustrate the issue, consider
the
Shapefile format: a 100 byte header followed by variable-length
records.
The tricky bit is
On Friday, 3 January 2014 at 23:14:31 UTC, monarch_dodra wrote:
In particular, arguably, input ranges that are also output
ranges are confusing, since rather than "growing as you add
items to their tip (what you'd want)", they instead "shrink as
you overwrite their front, until they are empty/
This piece (recently seen on the Hacker News front page):
http://rust-class.org/pages/using-rust-for-an-undergraduate-os-course.html
.. includes a pretty damning assessment of D as "unsafe"
(compared to Rust) and generally doomed. I remember hearing
Walter Bright talking a lot about "safe code
On Saturday, 4 January 2014 at 02:09:51 UTC, NoUseForAName wrote:
This piece (recently seen on the Hacker News front page):
http://rust-class.org/pages/using-rust-for-an-undergraduate-os-course.html
.. includes a pretty damning assessment of D as "unsafe"
(compared to Rust) and generally doome
Thanks!
On Saturday, 4 January 2014 at 02:09:51 UTC, NoUseForAName wrote:
.. includes a pretty damning assessment of D as "unsafe"
(compared to Rust) and generally doomed.
I'd say the author is simply wrong about the doomed thing, the
link he cites doesn't make a convincing case, and is many years
ol
On Saturday, 4 January 2014 at 02:09:51 UTC, NoUseForAName wrote:
This piece (recently seen on the Hacker News front page):
http://rust-class.org/pages/using-rust-for-an-undergraduate-os-course.html
.. includes a pretty damning assessment of D as "unsafe"
(compared to Rust) and generally doome
On Saturday, 4 January 2014 at 03:16:37 UTC, Jesse Phillips wrote:
Basically D provides safety, but it also provides means to do
unsafe things. I'm not familiar with Rust, but I wouldn't be
surprised if unsafe actions could also be taken.
Haha, he covers that in the next section, just before I
On Saturday, 4 January 2014 at 03:16:37 UTC, Jesse Phillips wrote:
Basically D provides safety, but it also provides means to do
unsafe things. I'm not familiar with Rust, but I wouldn't be
surprised if unsafe actions could also be taken.
You can still take unsafe actions, they just need to be
On Saturday, 4 January 2014 at 02:09:51 UTC, NoUseForAName wrote:
This piece (recently seen on the Hacker News front page):
http://rust-class.org/pages/using-rust-for-an-undergraduate-os-course.html
.. includes a pretty damning assessment of D as "unsafe"
(compared to Rust) and generally doome
On Saturday, 4 January 2014 at 02:27:24 UTC, Kelet wrote:
While `@safe` helps reduce this class of logic errors […]
you can still have […] dangling pointers, hence it is
usually considered inferior with regards to safety.
This is not true. While it _is_ possible to get null pointers in
@safe c
On Saturday, 4 January 2014 at 04:20:30 UTC, David Nadlinger
wrote:
On Saturday, 4 January 2014 at 02:27:24 UTC, Kelet wrote:
While `@safe` helps reduce this class of logic errors […]
you can still have […] dangling pointers, hence it is
usually considered inferior with regards to safety.
This
On 1/3/2014 6:27 PM, Kelet wrote:
With Rust, there are no dangling or null pointers. This means that if a pointer
exists, it points to a valid object of the appropriate type. When a pointer does
not point to a valid object of the appropriate type, accessing the content at
the pointer results in u
On 01/04/2014 05:31 AM, Walter Bright wrote:
...
Null pointers are not a safety issue.
In the general sense of the word, yes they are.
Safety means no memory corruption.
...
That's memory safety.
On Saturday, 4 January 2014 at 04:26:24 UTC, Kelet wrote:
Ultimately, it sounds like Rust primarily takes the 'default
on' approach for things like safety and immutability, whereas D
takes the 'default off' approach.
Sometimes the Rust approach is simply different. For instance,
Rust disables
On 1/3/2014 8:36 PM, Timon Gehr wrote:
On 01/04/2014 05:31 AM, Walter Bright wrote:
...
Null pointers are not a safety issue.
In the general sense of the word, yes they are.
Please explain.
On 12/29/2013 02:47 PM, "Ola Fosheim Grøstad"
" wrote:
On Sunday, 29 December 2013 at 20:36:27 UTC, Walter Bright wrote:
I'll reiterate that the GC will NEVER EVER pause your program unless
you are actually calling the GC to allocate memory. A loop that does
not GC allocate WILL NEVER PAUSE.
T
On Saturday, 4 January 2014 at 07:00:28 UTC, 1100110 wrote:
But in fact it's a very small subset. Hell, it's small enough
to be a *special case*.
No, real time applications are not a very small subset. Hard
real-time applications are in a smaller subset, although most
audio-applications for
On Saturday, 4 January 2014 at 05:16:38 UTC, Walter Bright wrote:
On 1/3/2014 8:36 PM, Timon Gehr wrote:
On 01/04/2014 05:31 AM, Walter Bright wrote:
...
Null pointers are not a safety issue.
In the general sense of the word, yes they are.
Please explain.
I don't know Timon Gehr's opinio
44 matches
Mail list logo
