Re: gl3n - linear algebra and more for D
On 12/2/2011 5:36 PM, David wrote: Hello, I am currently working on gl3n - https://bitbucket.org/dav1d/gl3n - gl3n provides all the math you need to work with OpenGL, DirectX or just vectors and matrices (it's mainly targeted at graphics - gl3n will never be more then a pure math library). What it supports: - dav1d I can see myself using this. Thanks for your work.
Re: std.dateparse reincarnation
On 10/25/2011 5:23 PM, Walter Bright wrote: Yes, but I've done a fair amount of delegating. Andrei is in charge of Phobos. Is there a list somewhere of who performs what roles, and what people are currently working on (and their queue)? Having something like this would be useful for potential contributors to find their niche.
Re: cuteDoc -New DDOC theme
On 10/28/2011 5:18 PM, Nick Sabalausky wrote: and then use JS Where is Nick Sabalausky and what have you done to him?
Re: D2 port of Tango
On 10/20/2011 12:38 PM, Eric Poggel (JoeCoder) wrote: On 10/18/2011 5:07 PM, SiegeLord wrote: to use it you'd install the whole thing somewhere on your computer. That's what I do now with Tango 1. But if every library I used required separate installation steps (instead of just pitting it in the repository), there would be about a dozen to install. I want to keep things as simple as possible for my users. My goal is to make it as easy as: 1. Install dmd 2. Checkout Yage from Hg 3. Run the build script Sorry, I don't mean to sound so demanding. I greatly appreciate your work in porting tango to D2.
Re: D2 port of Tango
On 10/18/2011 5:07 PM, SiegeLord wrote: to use it you'd install the whole thing somewhere on your computer. That's what I do now with Tango 1. But if every library I used required separate installation steps (instead of just pitting it in the repository), there would be about a dozen to install. I want to keep things as simple as possible for my users. My goal is to make it as easy as: 1. Install dmd 2. Checkout Yage from Hg 3. Run the build script
Re: D2 port of Tango
On 10/18/2011 12:45 PM, Trass3r wrote: I already mentioned this deeper down in the thread, but what are the chances of being able to use tango as an add-on for phobos2? Something from which I could pull in only the tango modules I need and use phobos for the rest? He already answered that: SiegeLord Wrote: Does this use druntime? Yes, although a Tango specific runtime (compatible with druntime) will probably be an option some day too. Still, right now you can safely use (modulo my imperfect testing) Phobos and Tango modules together in a single program. Not quite. I was wondering if it can be done with ONLY bringing in what I need, as apposed to most or all of tango.
Re: D2 port of Tango
On 10/18/2011 6:24 AM, Trass3r wrote: Why? What's the point? Why not work on Phobos instead? Well D1 projects could be ported to D2 much more easily, e.g. Yage. True, but I had hoped to port Yage to phobos2 anyway. Lack of xml support in phobos is the biggest reason I haven't started doing this already. Time being another reason. If Tango was a library of add-in modules of which I could include only what I need, I would be very likely to keep using it. I think tango could become quite popular again with an approach like this. But it may need to depend on some phobos modules and conventions for good integration.
Re: D2 port of Tango
On 10/18/2011 12:52 AM, SiegeLord wrote: I just wanted to get the word out about a little project me and a few other people been working on for the few past months, in case anyone feels like helping out (or just as an FYI). This project is the D2 port of the Tango framework library. You can read about it here: https://github.com/SiegeLord/Tango-D2 We are currently a little more than half way done in terms of modules fiddled with. Currently there are 181 modules ported out of approximately 343 (give or take 20). Currently only the dmd compiler and Linux platform are supported... but obviously we want to get all the other platforms/compilers as time goes on. I'm guessing at the current rate of porting we'll be done in about half a year. Now, the project is actually two projects in one. The first project is a D2 port proper that tries to keep API semantics the same as the D1 original. I preside over this aspect, and you can see the rough porting guidelines in the repository. This is the 'd2port' branch in my repository. The second project is a more ambitious effort to rewrite some aspects of Tango without preserving semantics or anything. mtachrono presides over this aspect, so you can talk to him about the motivations behind it. This is the 'master' branch in my repository. That's all. Cheers. -SiegeLord I already mentioned this deeper down in the thread, but what are the chances of being able to use tango as an add-on for phobos2? Something from which I could pull in only the tango modules I need and use phobos for the rest?
Re: Visual D 0.3.24 released
On 5/8/2011 5:31 AM, Rainer Schuetze wrote: Hi, as the newest version of Visual D includes some major improvements, I'd like to announce its release here. Visual D is a Visual Studio package providing both project management and language services for the D programming language. It works with Visual Studio 2005, 2008 and 2010 as well as the free Visual Studio Shells. Added features worth noting include * support for Object Browser and Class View * runs a parser in the background to underline syntax errors (no semantic analysis) * new version of the mago debugger that fixes some issues with exceptions and improves the call stack display Highlights in previous versions not announced here: * support for Code Definition Window * search and replace based on the D tokenizer, ignoring white spaces and comments and supporting brace matching * new compilation modes: compile and link seperately, compile only Visual D comes with an easy installer and can be downloaded here: http://www.dsource.org/projects/visuald Best, Rainer Thank you. This is great!
Re: Optlink 8.00.10
On 2/24/2011 8:14 PM, Walter Bright wrote: Walter Bright wrote: This fixes a couple of crashers, 2436 and 3372, that were causing people lots of trouble: http://ftp.digitalmars.com/link.8.00.10.zip More crashers fixed: http://ftp.digitalmars.com/link.8.00.11.zip Do these new versions use the in-progress C port? How is that going?
Re: New web newsreader - requesting participation
On 1/31/2011 5:28 PM, Walter Bright wrote: Adam Ruppe wrote: In the other newsgroup, I've been talking about a little web news program I've been writing as a spinoff of the potential new homepage idea. That is great news. I've been wanting to do one for years! I haven't looked much at yours yet, but here's my ideas anyway :-) 1. Can use web interface or nntp interface 2. web interface looks sort of like reddit, i.e. all posts on a thread 3. users can post anonymously 4. web interfaces supports logins - logged in users can vote up or down on posts 5. web interface can mark posts as read or unread - fixing my beef with reddit that there's no reasonable way to scan a thread for new posts 6. an easy way for moderators to delete spam 7. runs on 64 bit FreeBSD (what the Digital Mars server runs on), yes, I know that means I have to get 64 bit dmd on FreeBSD working! I can contribute the code that generates the D archive pages from the news postings. I hate to mention this in light of Adam's work, but Reddit is open source--why not run our own deployment of it for D? It seems that these changes would require minimal changes to the code base, except for nntp access. But I guess I don't understand the benefits of it over a web-based solution.
Re: DDT 0.4.0 released (formerly "Mmrnmhrm")
On 11/17/2010 1:52 PM, Bruno Medeiros wrote: I'm announcing the release of DDT (D Development Tools) version 0.4.0: http://code.google.com/a/eclipselabs.org/p/ddt/ (There was previously an older inactive project also called DDT, it has been renamed to EclipseD, with the authors permission.) The DDT project is a direct continuation of the Mmrnmhrm project. It has been renamed to reflect a more serious and unified approach to the Eclipse IDE project development. (although ocasional odd references might still be present in less conspicuous places ^_^ ) It has been 2 years since the last significant release, and this version has a lot of rough edges: Some newer D2 syntaxes are not yet supported (http://code.google.com/a/eclipselabs.org/p/ddt/issues/detail?id=6), and otherwise there are likely to be several parser bugs in the IDE (... you will be baked...). But it should provide for a minimally useful IDE, at least for simpler D projects. See http://code.google.com/a/eclipselabs.org/p/ddt/wiki/Features for a rough idea of what to expect. See also: http://code.google.com/a/eclipselabs.org/p/ddt/wiki/GeneralFAQ Changelog: == DDT 0.4.0 (2010-11-17) == * Renamed project to DDT * Updated IDE to latest DLTK version (2.0). * Fixed comment indentation character (was '#' instead of '//') on toggle comment actions * Fixed defaults bug in DeeRootPreferencePage and DeeEditorPreferencePage. * Added DEEBUILDER.COMPILEREXEPATH variable to builder, changed builder response file defaults. [No longer uses rebuild as the default] * Fixed parser to be able to parse expressions as the argument of typeid. * Added a parser workaround to allow parsing D source with annotations. * Fixed several parser bugs. * Removed Content Assist Templates preference page. I hope you're not discouraged by the lack of feedback. I'm hoping to switch to this project from Descent once it matures a little bit.
Re: New debugger coming soon!
On 8/9/2010 12:45 AM, Aldo Nunez wrote: I'll be posting the D debugger I've been working on at dsource this week. It'll be a set of debugging libraries that you can build your own debugger with, along with a Debug Engine plug-in for Visual Studio. I'll post another announcement as soon as it's available. It would also be great to have Descent integration (crosses fingers)
Re: D web site facelift
On 7/3/2010 5:48 AM, JimBob wrote: It's a bit bland, lacking in contrast between the colors. Makes me think of the colors of desert camoflage. What if the gray was changed to black? This would also help the menu contrast. I feel like the orange/red blended with gray looks a little muddy.
Re: dmd 1.062 and 2.047 release
On 6/15/2010 7:58 PM, strtr wrote: == Quote from BCS (n...@anon.com)'s article Hello Walter, strtr wrote: It's the optimization :) Without -O compilation took only a few seconds! Well, that explains it! Little attempt is made in the optimizer to make it compile faster if that would interfere with generating faster code. How does 1.061 w/ -O compare to 1.062 w/ -O? If 62 is much slower that might be of interest. That is exactly what I mentioned :? Or did you mean w/o ? In that case I don't much care it takes 5 or 10 seconds for thousands of lines of code :) (or, I don't know how to time dmd more precise than with my stopwatch when called through bud :D) Anyway, I kind of like that it takes longer now with optimization. I haven't checked whether things actually got any faster, but it feels a bit like in older games when it said: "Optimizing X for your computer" or "Generating A.I." :) "Reticulating Splines" was always my favorite.
Re: dmd 1.062 and 2.047 release
On 6/15/2010 5:58 AM, Jacob Carlborg wrote: On 2010-06-14 04:10, Eric Poggel wrote: On 6/13/2010 9:30 AM, Lutger wrote: Great, thank you! I noticed both std.concurrency and std.json are not (yet?) included in the documentation. Does that have any bearing on their status, are they usable and / or stable? There are some other modules without documentation like std.openrj and std.perf. Is there a page somewhere that documents their fate? I could only find this one: http://www.wikiservice.at/wiki4d/wiki.cgi?LanguageDevel Speaking of std.json, has anyone looked at the Orange library on dsource? http://www.dsource.org/projects/orange/ I haven't used it (yet), but it looks to support a back-end serialization engine that supports different front-ends, with xml currently being implemented. It's also Boost licensed. I would but it the other way around, a serialization front end with support for different back ends (archive types). I hope to add support for Phobos soon. Maybe I'm calling the front-end the back-end. Orange provides a reflection/serialization engine and allows for plugable serialization types--xml being the only one implemented so far.
Re: dmd 1.062 and 2.047 release
On 6/13/2010 9:30 AM, Lutger wrote: Great, thank you! I noticed both std.concurrency and std.json are not (yet?) included in the documentation. Does that have any bearing on their status, are they usable and / or stable? There are some other modules without documentation like std.openrj and std.perf. Is there a page somewhere that documents their fate? I could only find this one: http://www.wikiservice.at/wiki4d/wiki.cgi?LanguageDevel Speaking of std.json, has anyone looked at the Orange library on dsource? http://www.dsource.org/projects/orange/ I haven't used it (yet), but it looks to support a back-end serialization engine that supports different front-ends, with xml currently being implemented. It's also Boost licensed.
Re: Wormhol 1.0 released
On 4/8/2010 5:15 AM, #ponce wrote: Wormhol is a split-screen 3D snake game written in the D programming language. It Needs Windows, OpenGL 2.0. Download link: http://adinpsz.org/data/adinpsz_-_Wormhol.zip Pouet page: http://pouet.net/prod.php?which=54549 I'm very interested in getting bug reports, send me the log file log.htm Known bugs: - won't work on Intel cards - black screen on some ATI - sometimes don't start, depending of the directory Cheers, #ponce Beautiful game. Nice music too, where'd you get it? The only thing I'd change would be the textures in the 3d worlds, maybe an earth texture for the sphere, a dinner plate for the circle (with a kitchen skybox), and maybe make the odd shaped ones look like a snowflake. Just suggestions. My Specs: Athlon 2, 3 cores Ati Radeon 5600 Windows XP
Re: Wormhol 1.0 released
On 4/9/2010 1:03 PM, digited wrote: (why SDL?) I've been asking myself that same question. I realized a few months ago the only thing in Yage I use it for is to create a window and get input, and it's kind of sucky at window creation--you can't have more than one and switcing to/from fullscreen is buggy. NeHe's first tutorials already have code for window creation/input handling on Win/Linux/Mac, so that will probably what I go to.
Re: DMDScript now under Boost license
On 3/22/2010 3:30 AM, Walter Bright wrote: http://www.digitalmars.com/dscript/index.html Much appreciated! Also wondering how its performance compares against V8.
Re: Tango 0.99.9 Kai released
On 2/11/2010 9:14 AM, Moritz Warning wrote: On Thu, 11 Feb 2010 12:07:29 +0100, Jacob Carlborg wrote: On 2/11/10 06:11, strtr wrote: Nick Sabalausky Wrote: At the moment, no. Currently, Tango is D1-only, but druntime (the thing that is supposed to allow Tango and Phobos to play nice together on a single installation) is D2-only. So once Tango is ported to D2, I'd imagine there will probably be a Tango+DMD2 bundle that will include phobos and all your tango *and* phobos calls should work fine. But on D1, a DMD installation is either a tango one or a phobos one (unless you use some ugly hacks). I thought Tangobos was packaged in and would handle all Phobos calls without much hassle. Does it still work? Is it up to date ? Afaik, it's far from being up-to-date. Several months ago I got it up to date to work with the DMD + Tango 0.99.8 bundle (and committed my changes), and I'll check and fix it against Tango 0.99.9 when I get a chance, but I've been very busy lately so it may be weeks until I get to it. I'm not sure how it fares with GDC.
Re: CDC- Compile D Code
Anders F Björklund wrote: Eric Poggel wrote: CDC's only requirement is a D compiler. It is/will be supported on any operating system supported by the language. It works with dmd, ldc (soon), and gdc, phobos or tango. $ ./cdc -v cdc.d /usr/bin/ld: unknown flag: -ocdc Seems to be missing a space ? translate["-of"] = "-o"; Works OK on Mac OS X otherwise... (tested with Phobos if it matters) --anders Fixed. thanks for the bug report.
Re: CDC- Compile D Code
Michael P. wrote: Eric Poggel Wrote: Hello, I wrote a new build tool for D. I'm calling it CDC (for Compile D Code). It's hosted at http://dsource.org/projects/cdc . I'm open to any ideas or constructive criticism. My target here is anyone looking for a very simple build solution, not an everything and the kitchen sink project like DSSS (not that that's a bad thing). From the project description: This is a D programming language build script (and library) that can be used to compile D (version 1) source code. Unlike Bud, DSSS/Rebuild, Jake, and similar tools, CDC is contained within a single file that can easily be distributed with projects. This simplifies the build process since no other tools are required. The customBuild() function can be utilized to turn CDC into a custom build script for your project. CDC's only requirement is a D compiler. It is/will be supported on any operating system supported by the language. It works with dmd, ldc (soon), and gdc, phobos or tango. CDC can be used just like dmd, except for the following improvements. * CDC can accept paths as as well as individual source files for compilation. Each path is recursively searched for source, library, object, and ddoc files. * CDC automatically creates a modules.ddoc file for use with CandyDoc? and similar documentation utilities. * CDC defaults to use the compiler that was used to build itself. Compiler flags are passed straight through to that compiler. * The -op flag is always used, to prevent name conflicts in object and doc files. * Documentation files are all placed in the same folder with their full package names. This makes relative links between documents easier. It didn't build right away for me with DMD1.045 + Phobos. I changed line 141 which is: import std.c.time : sleep; to import std.c.time : sleep, usleep; And it built fine. The errors were: mich...@ubuntu:~/d/cdc/trunk$ dmd cdc.d cdc.d(623): Error: undefined identifier usleep cdc.d(623): Error: function expected before (), not usleep of type int Thanks. Your patch is now committed.
CDC- Compile D Code
Hello, I wrote a new build tool for D. I'm calling it CDC (for Compile D Code). It's hosted at http://dsource.org/projects/cdc . I'm open to any ideas or constructive criticism. My target here is anyone looking for a very simple build solution, not an everything and the kitchen sink project like DSSS (not that that's a bad thing). From the project description: This is a D programming language build script (and library) that can be used to compile D (version 1) source code. Unlike Bud, DSSS/Rebuild, Jake, and similar tools, CDC is contained within a single file that can easily be distributed with projects. This simplifies the build process since no other tools are required. The customBuild() function can be utilized to turn CDC into a custom build script for your project. CDC's only requirement is a D compiler. It is/will be supported on any operating system supported by the language. It works with dmd, ldc (soon), and gdc, phobos or tango. CDC can be used just like dmd, except for the following improvements. * CDC can accept paths as as well as individual source files for compilation. Each path is recursively searched for source, library, object, and ddoc files. * CDC automatically creates a modules.ddoc file for use with CandyDoc? and similar documentation utilities. * CDC defaults to use the compiler that was used to build itself. Compiler flags are passed straight through to that compiler. * The -op flag is always used, to prevent name conflicts in object and doc files. * Documentation files are all placed in the same folder with their full package names. This makes relative links between documents easier.
