Re: Some feedback on the website.

On 2015-12-16 14:50, Andrei Alexandrescu wrote: What standardized format was dominant in 2001? Thanks! -- Andrei 2001? According to the changelog Ddoc was added 2005 [1]. I hadn't really started to use D back then and barely programming at all. I would say Javadoc, Doxygen or Markdown,

Re: Some feedback on the website.

On Tuesday, 15 December 2015 at 21:45:02 UTC, deadalnix wrote: On Tuesday, 15 December 2015 at 13:42:29 UTC, Andrei Alexandrescu wrote: On 12/15/15 5:54 AM, tcak wrote: The harder it is made for people to contribute the system for fixations, the lesser changes are seen. I don't think we've

We need a good code font for the function signatures on dlang.org

I was looking at https://github.com/D-Programming-Language/dlang.org/pull/1169 and that bold sans serif proportional text for the code is just... well let's say it's time to replace it. What would be a good code font to use for those? Thanks, Andrei

Re: Some feedback on the website.

On 12/16/2015 03:59 PM, JohnCK wrote: On Wednesday, 16 December 2015 at 20:54:35 UTC, Walter Bright wrote: I'm not so sure... Like they say: "A father will never agree that his child is ugly!" To me it seems he's making a few good points. -- Andrei

Re: Some feedback on the website.

On Wednesday, 16 December 2015 at 19:12:04 UTC, H. S. Teoh wrote: On Wed, Dec 16, 2015 at 06:47:26PM +, deadalnix via Digitalmars-d wrote: [...] Using ddoc for the website may be NIH, but the ability to easily display snippets of D code without jumping through hoops is a big plus.

Re: Template parameter-dependent attributes

On 12/16/2015 06:14 PM, Andrei Alexandrescu wrote: So, I wrote this beautiful BigO framework: <400 lines all told, clear code, real nice. Then I got this cold shower: void insertFrontMany(C, R)(C container, R range) @BigO(complexity!(C.insertFront) * linearTime) { ... } My hope being

Re: Error 42: Symbol Undefined __lseeki64

On Wednesday, 16 December 2015 at 18:21:33 UTC, Byron Heads wrote: On Wednesday, 16 December 2015 at 18:14:35 UTC, Byron Heads wrote: On Wednesday, 16 December 2015 at 17:23:15 UTC, Byron Heads wrote: Seeing this issue on 2.069.2 using etc.c.zlib.

Re: And yet another cool project: fetching multiple URLs at once

On Wednesday, 16 December 2015 at 20:09:23 UTC, Sebastiaan Koppe wrote: But do you really want to put a ODBC client in there, as an example? Not sure if you're being serious making a joke, because that exists and Andrei was the one who made it http://dlang.org/phobos/etc_c_odbc_sql.html

Re: We need better documentation for functions with ranges and templates

On Wednesday, 16 December 2015 at 18:25:31 UTC, Luís Marques wrote: On Monday, 14 December 2015 at 19:04:46 UTC, bachmeier wrote: Something has to be done with the documentation for Phobos functions that involve ranges and templates. Just today: - "Where's the documentation for makeIndex?"

Re: isBidirectionalRange fails for unknown reasons

On Wednesday, 16 December 2015 at 20:43:02 UTC, Jack Stouffer wrote: unittest { static assert(isInputRange!(ReferenceInputRange!int)); // works static assert(isForwardRange!(ReferenceForwardRange!int)); // works static

Re: Some feedback on the website.

On 2015-12-16 20:33, Andrei Alexandrescu wrote: What's the issue there? -- Andrei One problem is that it doesn't work for symbols arbitrary nested packages. That is, XREF only forks for "a.b.c" not "a.b.c.d". -- /Jacob Carlborg

Re: Some feedback on the website.

On 12/16/2015 5:50 AM, Andrei Alexandrescu wrote: On 12/16/15 3:00 AM, Jacob Carlborg wrote: On 2015-12-16 02:15, Andrei Alexandrescu wrote: It seems knowing ddoc is part of knowing D. -- Andrei I'm wondering how you can think it's perfectly acceptable to invent our own (crappy) language

Re: Implicit Interface Deduction

On Sunday, 13 December 2015 at 22:09:47 UTC, Faux Amis wrote: interface IA {} interface IB {} interface IC {} interface IAB : IA, IB {} interface IBC : IB, IC {} class C : IA, IB, IC {} // Defining C as : IAB, IBC // is not really scalable ;) void main() { IAB c = new C(); // This doesn't

Re: Some feedback on the website.

On Wed, Dec 16, 2015 at 02:33:15PM -0500, Andrei Alexandrescu via Digitalmars-d wrote: > On 12/16/2015 02:12 PM, H. S. Teoh via Digitalmars-d wrote: > > the ongoing fiasco with XREF, LREF, whatever-REF and the > >associated relative/absolute URL nightmare > > What's the issue there? -- Andrei

Re: Some feedback on the website.

On 2015-12-16 20:12, H. S. Teoh via Digitalmars-d wrote: Using ddoc for the website may be NIH, but the ability to easily display snippets of D code without jumping through hoops is a big plus. Trying to do syntax-highlighted D code in plain HTML (or any other web authoring system, for that

Re: Wishlist for D

On Tuesday, 1 December 2015 at 16:48:00 UTC, Suliman wrote: Right place is write here My wish: New `std.io` package that includes `std.file`, `std.path` and `std.stdio` modules.

Re: Some feedback on the website.

On Wednesday, 16 December 2015 at 19:44:13 UTC, Jacob Carlborg wrote: There's DScanner [1]. [1] https://github.com/Hackerpilot/Dscanner/#syntax-highlighting Aye, and post-processing html to clean up the edge cases, reuse headers, etc. is really easy to do - easier than running bleeding-edge

Re: Some feedback on the website.

On Wednesday, 16 December 2015 at 20:54:35 UTC, Walter Bright wrote: I'm not so sure... Like they say: "A father will never agree that his child is ugly!" :) John.

Re: Some feedback on the website.

On 12/16/2015 03:05 PM, Vladimir Panteleev wrote: DDoc itself is very simple. The problem is the endless number of macros we use on dlang.org. I see that as a blessing. E.g. all the different ways to link to something: A, AHTTP, AHTTPS, ALOCAL, LINK, LINK2, WEB, LREF, XREF, XREF2, CXREF,

Re: And yet another cool project: fetching multiple URLs at once

On Wednesday, 16 December 2015 at 21:00:55 UTC, Andrei Alexandrescu wrote: I should add I've argued for including some of the core vibe.d stuff in Phobos. Sadly nobody is championing such a project for the time being. Andrei Would that include its stream stuff? We've been needing a

Re: Some feedback on the website.

On 12/16/2015 02:12 PM, H. S. Teoh via Digitalmars-d wrote: the ongoing fiasco with XREF, LREF, whatever-REF and the associated relative/absolute URL nightmare What's the issue there? -- Andrei

Re: And yet another cool project: fetching multiple URLs at once

On 12/16/2015 02:12 PM, Sebastiaan Koppe wrote: I think what I am trying to say is that a lot of stuff is already available on code.dlang.org, just not in phobos. Which begs the question, should it be? And if it does, shouldn't you rather consider merging vibe.d with phobos? Or parts of it?

Re: And yet another cool project: fetching multiple URLs at once

On Wednesday, 16 December 2015 at 19:32:36 UTC, Andrei Alexandrescu wrote: On 12/16/2015 02:12 PM, Sebastiaan Koppe wrote: I think what I am trying to say is that a lot of stuff is already available on code.dlang.org, just not in phobos. Which begs the question, should it be? And if it does,

isBidirectionalRange fails for unknown reasons

I'm trying to add a ReferenceBidirectionalRange range type to std.internal.test.dummyrange so I can test some range code I'm writing, but I've hit a wall and I'm not sure why. For some reason, the isBidirectionalRange check fails even though back and popBack are present. Any help here would be

Re: Some feedback on the website.

On 12/15/2015 12:31 AM, Gary Willoughby wrote: We've all said time and time again if ddoc wasn't used for the entire site more people would help with it. Ddoc makes sense for the documentation but not everything else. I'm not so sure. There are lots of tools to develop websites. Let's say A,

Re: Some feedback on the website.

On 12/16/2015 12:21 AM, ZombineDev wrote: Well DDoc may have it's disadvantages, but I'm certain that the documentation would have been far worse if it wasn't for it. No need to speculate :-) Before Ddoc, the Phobos documentation was horrific, probably the worst I'd ever seen. It was so bad

Re: And yet another cool project: fetching multiple URLs at once

On 12/16/2015 03:09 PM, Sebastiaan Koppe wrote: But do you really want to put a ODBC client in there, as an example? Or a grayscale filter? ODBC maybe, grayscale filter probably not. I should add I've argued for including some of the core vibe.d stuff in Phobos. Sadly nobody is championing

Re: Some feedback on the website.

On Wed, Dec 16, 2015 at 08:05:03PM +, Vladimir Panteleev via Digitalmars-d wrote: > On Tuesday, 15 December 2015 at 21:45:02 UTC, deadalnix wrote: > >On Tuesday, 15 December 2015 at 13:42:29 UTC, Andrei Alexandrescu wrote: > >>On 12/15/15 5:54 AM, tcak wrote: > >>>The harder it is made for

Re: Some feedback on the website.

On Wednesday, 16 December 2015 at 20:59:46 UTC, JohnCK wrote: On Wednesday, 16 December 2015 at 20:54:35 UTC, Walter Bright wrote: I'm not so sure... Like they say: "A father will never agree that his child is ugly!" :) John. Please don't go there. This is not about if ddoc is good or

Re: Some feedback on the website.

On Wednesday, 16 December 2015 at 21:06:48 UTC, Andrei Alexandrescu wrote: On 12/16/2015 03:59 PM, JohnCK wrote: On Wednesday, 16 December 2015 at 20:54:35 UTC, Walter Bright wrote: I'm not so sure... Like they say: "A father will never agree that his child is ugly!" To me it seems he's

[Issue 10193] Template args to UDA's

https://issues.dlang.org/show_bug.cgi?id=10193 Andrei Alexandrescu changed: What|Removed |Added CC||and...@erdani.com

[Issue 13301] Inline ASM documentation does not allow string literals

https://issues.dlang.org/show_bug.cgi?id=13301 Mathias Lang changed: What|Removed |Added Status|NEW |RESOLVED

Re: Some feedback on the website.

On Wednesday, 16 December 2015 at 18:47:26 UTC, deadalnix wrote: On Wednesday, 16 December 2015 at 13:52:05 UTC, Andrei Alexandrescu wrote: What would you have done instead? Honestly for D code itself, ddoc does just fine, but for the website, plain html or some known template format like .

Re: Another cool project: make double.to!string CTFEable

On Wednesday, 16 December 2015 at 15:44:45 UTC, Andrei Alexandrescu wrote: This has been discussed in the past and at a point Walter was looking into it. Currently std.conv.to applied to double uses snprintf, which is obviously non-CTFEable. There's been recent work (also discussed here) on

Re: Voting For std.experimental.ndslice

On Wednesday, 16 December 2015 at 17:49:03 UTC, Ilya Yaroshenko wrote: On Wednesday, 16 December 2015 at 11:01:25 UTC, Robert burner Schadek wrote: I have not found examples where string mixins can be removed. Please refer to particular example. The code for `sliced` and `assumeSorted` looks

[Issue 15457] New: Symbol Undefined __lseeki64

https://issues.dlang.org/show_bug.cgi?id=15457 Issue ID: 15457 Summary: Symbol Undefined __lseeki64 Product: D Version: D2 Hardware: x86 OS: Windows Status: NEW Severity: normal Priority: P1

Re: We need better documentation for functions with ranges and templates

On Monday, 14 December 2015 at 19:04:46 UTC, bachmeier wrote: Something has to be done with the documentation for Phobos functions that involve ranges and templates. Just today: - "Where's the documentation for makeIndex?" - http://imgur.com/4SQckvN - "AHH!" *runs away*

[Issue 10233] [Tracker] Grammar issues

https://issues.dlang.org/show_bug.cgi?id=10233 Issue 10233 depends on issue 13302, which changed state. Issue 13302 Summary: Inline ASM grammar is not left-associative https://issues.dlang.org/show_bug.cgi?id=13302 What|Removed |Added

Template parameter-dependent attributes

So, I wrote this beautiful BigO framework: <400 lines all told, clear code, real nice. Then I got this cold shower: void insertFrontMany(C, R)(C container, R range) @BigO(complexity!(C.insertFront) * linearTime) { ... } My hope being of course that for containers with linear insertion

Re: Template parameter-dependent attributes

On 12/16/2015 06:46 PM, Daniel N wrote: On Wednesday, 16 December 2015 at 17:14:50 UTC, Andrei Alexandrescu wrote: So... attributes are currently not allowed to depend on template parameters, which is a serious damper on enthusiasm. Indeed, please see the discussion in:

[Issue 13302] Inline ASM grammar is not left-associative

https://issues.dlang.org/show_bug.cgi?id=13302 Mathias Lang changed: What|Removed |Added Status|NEW |RESOLVED

Re: Some feedback on the website.

On Wednesday, 16 December 2015 at 13:52:05 UTC, Andrei Alexandrescu wrote: Also, ddoc always appeared to me like a big NIH syndrome. What would you have done instead? Honestly for D code itself, ddoc does just fine, but for the website, plain html or some known template format like . This

[Issue 13327] Specification of anonymous enum with one member is missed

https://issues.dlang.org/show_bug.cgi?id=13327 Mathias Lang changed: What|Removed |Added Status|NEW |RESOLVED

[Issue 10233] [Tracker] Grammar issues

https://issues.dlang.org/show_bug.cgi?id=10233 Issue 10233 depends on issue 13327, which changed state. Issue 13327 Summary: Specification of anonymous enum with one member is missed https://issues.dlang.org/show_bug.cgi?id=13327 What|Removed |Added

Re: Some feedback on the website.

On Wed, Dec 16, 2015 at 06:47:26PM +, deadalnix via Digitalmars-d wrote: > On Wednesday, 16 December 2015 at 13:52:05 UTC, Andrei Alexandrescu wrote: > >>Also, ddoc always appeared to me like a big NIH syndrome. > > > >What would you have done instead? > > > > Honestly for D code itself, ddoc

Re: Segfault while compiling simple program

I tested it on linux (64-bit distro), and it segfaults as well: - $ echo "struct S { ushort a, b; ubyte c, d; } struct T { ushort e; S s; }" > test.d $ dmd -v test.d binarydmd version v2.069.0 config/etc/dmd.conf parse test importall test importobject

Re: Template parameter-dependent attributes

On Wednesday, 16 December 2015 at 17:14:50 UTC, Andrei Alexandrescu wrote: So... attributes are currently not allowed to depend on template parameters, which is a serious damper on enthusiasm. Indeed, please see the discussion in: https://issues.dlang.org/show_bug.cgi?id=10193 /Daniel

[Issue 10233] [Tracker] Grammar issues

https://issues.dlang.org/show_bug.cgi?id=10233 Issue 10233 depends on issue 13301, which changed state. Issue 13301 Summary: Inline ASM documentation does not allow string literals https://issues.dlang.org/show_bug.cgi?id=13301 What|Removed |Added

[Issue 15456] sc.ini: Access denied for non-superusers on Windows 10

https://issues.dlang.org/show_bug.cgi?id=15456 Brad Anderson changed: What|Removed |Added CC||e...@gnuk.net --- Comment #1

Re: Another cool project: make double.to!string CTFEable

On 12/16/2015 12:04 PM, tcak wrote: On Wednesday, 16 December 2015 at 15:44:45 UTC, Andrei Alexandrescu wrote: This has been discussed in the past and at a point Walter was looking into it. Currently std.conv.to applied to double uses snprintf, which is obviously non-CTFEable. There's been

Error 42: Symbol Undefined __lseeki64

Seeing this issue on 2.069.2 using etc.c.zlib. C:\d\dmd2\windows\bin\..\lib\phobos.lib(gzlib) Error 42: Symbol Undefined __lseeki64 The code was compiling in 2.067. Not clear on where to look to fix this issue.

Re: Error 42: Symbol Undefined __lseeki64

On Wednesday, 16 December 2015 at 17:23:15 UTC, Byron Heads wrote: Seeing this issue on 2.069.2 using etc.c.zlib. C:\d\dmd2\windows\bin\..\lib\phobos.lib(gzlib) Error 42: Symbol Undefined __lseeki64 The code was compiling in 2.067. Not clear on where to look to fix this issue. I can

Re: Voting For std.experimental.ndslice

On Wednesday, 16 December 2015 at 11:01:25 UTC, Robert burner Schadek wrote: Yes with many conditions: * Documentation ** The documentation needs a complete rewrite. If I hadn't had any prior knowledge, I would have needed to read the numpy documentation to figure what this package does. That

Re: Error 42: Symbol Undefined __lseeki64

On Wednesday, 16 December 2015 at 18:14:35 UTC, Byron Heads wrote: On Wednesday, 16 December 2015 at 17:23:15 UTC, Byron Heads wrote: Seeing this issue on 2.069.2 using etc.c.zlib. C:\d\dmd2\windows\bin\..\lib\phobos.lib(gzlib) Error 42: Symbol Undefined __lseeki64 The code was compiling in

Re: And yet another cool project: fetching multiple URLs at once

On Wednesday, 16 December 2015 at 15:54:09 UTC, Andrei Alexandrescu wrote: Right now we can nicely stream an URL as an input range. A great extension would be to fetch several URLs at once. When accessing r.front for that range, the user gets a pair of URL and data chunk. Of course the point

Re: We need a good code font for the function signatures on dlang.org

On Wed, Dec 16, 2015 at 04:05:27PM -0500, Andrei Alexandrescu via Digitalmars-d wrote: > I was looking at > https://github.com/D-Programming-Language/dlang.org/pull/1169 and that > bold sans serif proportional text for the code is just... well let's > say it's time to replace it. > > What would

Re: We need better documentation for functions with ranges and templates

On Thu, Dec 17, 2015 at 12:00:03AM +0100, Timon Gehr via Digitalmars-d wrote: > On 12/15/2015 12:26 PM, rumbu wrote: > > > >And personally, I found the MS remark more compact and more user > >friendly than: > > > >"This is a best-effort implementation of length for any kind of > >range. If

Re: Some feedback on the website.

On 12/16/2015 05:32 PM, H. S. Teoh via Digitalmars-d wrote: While I'm on the fence about the value of ddoc as a website programming language (not as a documentation generator, where it is excellent IMO), I'm doubtful of the value of converting wholesale to a different format at this present

Re: Some feedback on the website.

On Wed, Dec 16, 2015 at 01:00:19PM -0800, Walter Bright via Digitalmars-d wrote: > On 12/16/2015 12:21 AM, ZombineDev wrote: > >Well DDoc may have it's disadvantages, but I'm certain that the > >documentation would have been far worse if it wasn't for it. > > No need to speculate :-) Before Ddoc,

Re: Some feedback on the website.

On 12/16/2015 7:32 AM, Jack Stouffer wrote: 3. "Who wants to spend hours and hours of work writing a DDoc to Markdown converter or manually convert all existing pages? Do we have any volunteers?" I can't even get consistent documentation of the parameters to a function: For example:

Re: Some feedback on the website.

On Wednesday, 16 December 2015 at 21:57:05 UTC, Walter Bright wrote: On 12/16/2015 7:32 AM, Jack Stouffer wrote: 3. "Who wants to spend hours and hours of work writing a DDoc to Markdown converter or manually convert all existing pages? Do we have any volunteers?" I can't even get consistent

Re: Some feedback on the website.

On Wed, Dec 16, 2015 at 10:00:50PM +, Meta via Digitalmars-d wrote: > On Wednesday, 16 December 2015 at 21:57:05 UTC, Walter Bright wrote: [...] > >There's plenty to be done to improve things that converting all the > >pages to another format will not help with. While I'm on the fence about

Re: We need better documentation for functions with ranges and templates

On 12/15/2015 12:26 PM, rumbu wrote: And personally, I found the MS remark more compact and more user friendly than: "This is a best-effort implementation of length for any kind of range. If hasLength!Range, simply returns range.length without checking upTo (when specified). Otherwise, walks

Re: Some feedback on the website.

On 12/16/2015 04:09 PM, H. S. Teoh via Digitalmars-d wrote: Also, the lack of flexibility in number of macro arguments means you end up with LINK, LINK2, LINK3, etc., with no obvious indication what the difference is and where you should use which macro. (Well the obvious indication is the

Re: Some feedback on the website.

On Wednesday, 16 December 2015 at 23:01:47 UTC, Walter Bright wrote: Exactly. We'll never get anywhere chasing people who say "I'll help only if you convert to my way of doing things." I've done enough of that in the past, and concluded they're just seeing how long you'll dance to their tune

Re: Some feedback on the website.

On 12/16/2015 3:43 PM, BLM768 wrote: One is to make as much of it as possible in plain old static HTML. I've done that before, a lot. Ddoc cut the work involved in that in half, and I mean in half. It also made it easy to change the look of a whole site, rather than being a mess of tedium.

Re: We need a good code font for the function signatures on dlang.org

On Wednesday, 16 December 2015 at 21:05:27 UTC, Andrei Alexandrescu wrote: I was looking at https://github.com/D-Programming-Language/dlang.org/pull/1169 and that bold sans serif proportional text for the code is just... well let's say it's time to replace it. What would be a good code font

Re: Some feedback on the website.

On Wednesday, 16 December 2015 at 21:30:32 UTC, H. S. Teoh wrote: I don't think anybody is questioning the value of ddoc as a *documentation generator*. The issue here is whether it has the same value as a *website programming language*. Very different things. That I agree! JohnCK.

Re: We need a good code font for the function signatures on dlang.org

On 12/16/2015 04:40 PM, Jack Stouffer wrote: On Wednesday, 16 December 2015 at 21:05:27 UTC, Andrei Alexandrescu wrote: I was looking at https://github.com/D-Programming-Language/dlang.org/pull/1169 and that bold sans serif proportional text for the code is just... well let's say it's time to

Re: We need a good code font for the function signatures on dlang.org

On 12/16/2015 04:32 PM, H. S. Teoh via Digitalmars-d wrote: On Wed, Dec 16, 2015 at 04:05:27PM -0500, Andrei Alexandrescu via Digitalmars-d wrote: I was looking at https://github.com/D-Programming-Language/dlang.org/pull/1169 and that bold sans serif proportional text for the code is just...

Re: Some feedback on the website.

On 12/16/2015 04:17 PM, deadalnix wrote: In that regard, I think it is fair to asses that people that know webdev don't know ddoc an vice versa. So using ddoc is probably not the best bet here. Yah, agreed (though I have to say it's not that fair to my tushy :o)). -- Andrei

Re: Some feedback on the website.

On 12/16/2015 06:29 PM, H. S. Teoh via Digitalmars-d wrote: Allow overloading by number of arguments, maybe? (This sounds suspiciously like a slippery slope, though...) That'll have trouble with $0 and $+. Or allow argument list slicing, D-style? Not sure if this would solve all the

Re: Some feedback on the website.

On 12/16/2015 06:43 PM, BLM768 wrote: One is to make as much of it as possible in plain old static HTML. Stuff like the articles rarely changes, after all. But I dislike typing HTML. DDoc improves on that significantly. Another idea is to use a Web application framework. There's a

Re: Some feedback on the website.

On Wednesday, 16 December 2015 at 23:43:41 UTC, BLM768 wrote: [snip] ...and as I read some older posts, I see that mine is completely redundant. ;) Seriously, though, I'm willing to help prototype something. I've got time before the next semester starts.

Re: We need better documentation for functions with ranges and templates

On Wednesday, 16 December 2015 at 18:25:31 UTC, Luís Marques wrote: On Monday, 14 December 2015 at 19:04:46 UTC, bachmeier wrote: Something has to be done with the documentation for Phobos functions that involve ranges and templates. Just today: - "Where's the documentation for makeIndex?"

Re: Some feedback on the website.

On Wed, Dec 16, 2015 at 03:04:51PM -0800, Walter Bright via Digitalmars-d wrote: > On 12/16/2015 12:59 PM, JohnCK wrote: > >On Wednesday, 16 December 2015 at 20:54:35 UTC, Walter Bright wrote: > >>I'm not so sure... > > > >Like they say: "A father will never agree that his child is ugly!" > > >

Re: Some feedback on the website.

On Wednesday, 16 December 2015 at 21:18:43 UTC, JohnCK wrote: On Wednesday, 16 December 2015 at 21:06:48 UTC, Andrei Alexandrescu wrote: On 12/16/2015 03:59 PM, JohnCK wrote: On Wednesday, 16 December 2015 at 20:54:35 UTC, Walter Bright wrote: I'm not so sure... Like they say: "A father

Re: Some feedback on the website.

On Wednesday, 16 December 2015 at 21:17:43 UTC, deadalnix wrote: On Wednesday, 16 December 2015 at 20:59:46 UTC, JohnCK wrote: On Wednesday, 16 December 2015 at 20:54:35 UTC, Walter Bright wrote: I'm not so sure... Like they say: "A father will never agree that his child is ugly!" :)

Re: We need a good code font for the function signatures on dlang.org

On Wednesday, 16 December 2015 at 21:05:27 UTC, Andrei Alexandrescu wrote: I was looking at https://github.com/D-Programming-Language/dlang.org/pull/1169 and that bold sans serif proportional text for the code is just... well let's say it's time to replace it. What would be a good code font

Re: isBidirectionalRange fails for unknown reasons

On 16.12.2015 21:43, Jack Stouffer wrote: I'm trying to add a ReferenceBidirectionalRange range type to std.internal.test.dummyrange so I can test some range code I'm writing, but I've hit a wall and I'm not sure why. For some reason, the isBidirectionalRange check fails even though back and

Re: isBidirectionalRange fails for unknown reasons

On Wednesday, 16 December 2015 at 21:40:44 UTC, anonymous wrote: The `.save` primitive of forward ranges must return the very same type that the range has. But your ReferenceBidirectionalRange!T.save returns a ReferenceForwardRange!T, because it's inherited. That makes

Re: Some feedback on the website.

On Wed, Dec 16, 2015 at 12:54:35PM -0800, Walter Bright via Digitalmars-d wrote: [...] > I do agree that the macros defined in the site's .ddoc files are > ridiculously overlapping, redundant, etc. That all could use a > redesign and an overhaul, but that isn't Ddoc's fault. It's just like > any

Re: We need a good code font for the function signatures on dlang.org

On Wednesday, 16 December 2015 at 21:40:13 UTC, Jack Stouffer wrote: On Wednesday, 16 December 2015 at 21:05:27 UTC, Andrei Alexandrescu wrote: I was looking at https://github.com/D-Programming-Language/dlang.org/pull/1169 and that bold sans serif proportional text for the code is just...

Re: Another cool project: make double.to!string CTFEable

On 12/16/2015 06:04 PM, tcak wrote: On Wednesday, 16 December 2015 at 15:44:45 UTC, Andrei Alexandrescu wrote: This has been discussed in the past and at a point Walter was looking into it. Currently std.conv.to applied to double uses snprintf, which is obviously non-CTFEable. There's been

Re: Some feedback on the website.

On 12/16/2015 2:32 PM, H. S. Teoh via Digitalmars-d wrote: I'm doubtful of the value of converting wholesale to a different format at this present time. That's a lot of effort and drain of our scant resources, with only unverifiable claims of increased participation from nebulous crowds who so

Re: Some feedback on the website.

On 12/16/2015 12:59 PM, JohnCK wrote: On Wednesday, 16 December 2015 at 20:54:35 UTC, Walter Bright wrote: I'm not so sure... Like they say: "A father will never agree that his child is ugly!" :) I've pontificated before about design mistakes in D that I've made. I also think that a lot

Re: Some feedback on the website.

On Wed, Dec 16, 2015 at 06:18:22PM -0500, Andrei Alexandrescu via Digitalmars-d wrote: > On 12/16/2015 04:09 PM, H. S. Teoh via Digitalmars-d wrote: > >Also, the lack of flexibility in number of macro arguments means you > >end up with LINK, LINK2, LINK3, etc., with no obvious indication what >

Re: No documentation for core.sys?

On Thursday, 17 December 2015 at 03:40:02 UTC, Shriramana Sharma wrote: In my recent search for D's equivalent of isatty, I found out that there is a core.sys.posix module only by rgrepping under /usr/include/dmd. Why isn't there a documentation page http://dlang.org/phobos/core_sys.html

Re: Using a struct as a wrapper for an extern(C) opaque type, no default constructor, what do?

On Thursday, 17 December 2015 at 03:43:58 UTC, Jakob Ovrum wrote: On Thursday, 17 December 2015 at 03:31:37 UTC, Jeremy DeHaan wrote: Hi all. I'm interfacing to some C code which include an opaque type and some C functions that create and work with a pointer to that type. I want to wrap up

Re: Using a struct as a wrapper for an extern(C) opaque type, no default constructor, what do?

On Thursday, 17 December 2015 at 04:05:30 UTC, Jeremy DeHaan wrote: http://dpaste.com/3FH3W13 Also, I would be wary of lazy initialization. We have bad experiences with it for AAs and standard containers. A typical example would be: void foo(Wrapper w) { ... w.doTheThing(); ...

Re: Using a struct as a wrapper for an extern(C) opaque type, no default constructor, what do?

On Thursday, 17 December 2015 at 04:05:30 UTC, Jeremy DeHaan wrote: Thanks. I guess what bugs me is that I always try to hide the fact that the API is a wrapper around C stuff, ie, I want to make people feel as though they're using idiomatic D. Doing something like this makes it feel like less

Re: And yet another cool project: fetching multiple URLs at once

On Wednesday, 16 December 2015 at 21:00:55 UTC, Andrei Alexandrescu wrote: On 12/16/2015 03:09 PM, Sebastiaan Koppe wrote: But do you really want to put a ODBC client in there, as an example? Or a grayscale filter? ODBC maybe, grayscale filter probably not. I should add I've argued for

Re: Using a struct as a wrapper for an extern(C) opaque type, no default constructor, what do?

On Thursday, 17 December 2015 at 06:04:14 UTC, Jeremy DeHaan wrote: And I guess what I was talking about before is that using a factory method feels klunky to me. If the things I am wrapping had been written in D they could use default initialization, so it feels wrong to do otherwise. I also

Re: We need better documentation for functions with ranges and templates

On Monday, 14 December 2015 at 19:04:46 UTC, bachmeier wrote: Something has to be done with the documentation for Phobos functions that involve ranges and templates. Many useful ideas in this thread. One I don't recall seeing - a standard way to denote whether a routine is lazy or eager. I'm

Re: Why should file names intended for executables be valid identifiers?

Adam D. Ruppe wrote: > It still has a module name that can be used in reflection, must > be used in name disambiguation (at the linker level if nothing > else, any functions are mangled with the module name so they > don't conflict with C functions with the same name), and other > things. Sorry

Re: No documentation for core.sys?

On Thursday, 17 December 2015 at 04:23:30 UTC, Shriramana Sharma wrote: Jakob Ovrum wrote: As with core.stdc, refer to the documentation for the equivalent C header. I only know of even core.stdc's existence since I've been poking into the Phobos sources. At least the Phobos documentation

Re: Error 42: Symbol Undefined __lseeki64

On Wednesday, 16 December 2015 at 18:30:41 UTC, Byron Heads wrote: On Wednesday, 16 December 2015 at 18:21:33 UTC, Byron Heads wrote: On Wednesday, 16 December 2015 at 18:14:35 UTC, Byron Heads wrote: [...] Commenting out gzclose(fpGZip); allows it to compile.. Submitted reduced case as

Re: We need better documentation for functions with ranges and templates

On Thursday, 17 December 2015 at 00:06:05 UTC, John Colvin wrote: Given a running time R(n), the time-complexity is given by O(f(n)) iff df/dn = lim_{n -> inf} dR(n)/dn Is that also a correct expression? Obviously I'm papering over the discretisation, but well, I did say physicist... :)

Re: Testing if a file is connected to a terminal

On Thursday, 17 December 2015 at 04:05:57 UTC, Adam D. Ruppe wrote: On Thursday, 17 December 2015 at 03:59:27 UTC, Jakob Ovrum wrote: There are some terminal libraries on Github (like consoled) but I have to say I think they're uninspiring in terms of quality and presentation. Can you be any

Re: Testing if a file is connected to a terminal

Jakob Ovrum wrote: > Where's the reference documentation? There's a README: http://code.dlang.org/packages/consoled, and the source does seem to have DDoc comments... -- Shriramana Sharma, Penguin #395953

  1   2   >