Re: DCD 0.3.0-beta1 and DScanner 0.1.0-beta1

[Suliman]

On Wednesday, 29 January 2014 at 07:52:20 UTC, yazd wrote:

On Wednesday, 29 January 2014 at 06:53:34 UTC, Suliman wrote:

Look like I was need to write
C:\\D\\dmd2\\windows\\bin\\
instead of C:\\D\\dmd2\\windows\\bin

Thanks! All work!


That's weird. Anyway, if you would like to help with Windows 
setup, please submit your difficulties in a pull request to 
update the README, or point in them in the issue tracker on 
github as I have not personally run the plugin on a Windows 
machine.


Again my issue. All work without \\ at the end! thanks for help!

Re: dmd 2.065 beta 2

[Benjamin Thaut]

Am 29.01.2014 08:43, schrieb deadalnix:


Awesome, that compile my code and test suite are passing. Everything
looks good !


As usual, my code doesn't compile. I filed a bug report:
https://d.puremagic.com/issues/show_bug.cgi?id=12023

Re: DCD 0.3.0-beta1 and DScanner 0.1.0-beta1

[fra]

Vim plugin seems to be in a messy state right now.
Completion only works after a dot, and even then it produces
strange output on the dcd-server logging window. Perhaps in needs
some update due to changes to the server and client code?

Re: D bindings for Shapefile C Library

[Rikki Cattermole]

On Wednesday, 29 January 2014 at 06:55:17 UTC, evilrat wrote:
On Wednesday, 29 January 2014 at 05:12:45 UTC, Rikki Cattermole 
wrote:


For simple static bindings, it looks fine. You'll probably 
have fun getting it to work on Windows 32 bit though. Thank 
you OMF.


what fun? using (coff)implib once? come on, that's not that 
hard at all...


the only fun is when lib export only constants which is rare.


I'm just referring to it being messier than it needs to be. This 
is a little pet peeve of mine.

COMPO - 2.064

[Steve Teale]

I pushed changes to GitHub (https://github.com/britseye/compo) 
today that allow a clean build with warnings and deprecations on 
using DMD2.064.


Regularized shape and geometric objects so they are all 
implemented

in a similar way for ease of maintenance.

Added a more complete implementation of Flatten and Drawing, and 
a new
pattern type - BrushDabs. This introduces the idea of 'shim' 
layers -

objects that do not normally display themselves, but effect the
following layer. So BrushDabs will be used as fill for any closed 
shape

or geometric object that is placed over it.

The Codeblocks project file is also changed somewhat - hopefully 
for the better. Codeblocks linking is very fragile.

Re: D bindings for Shapefile C Library

[Sönke Ludwig]

Am 29.01.2014 05:24, schrieb Craig Dillabaugh:

I've created bindings for the C Shapefile Library.  Shapefiles
are a format used commonly in vector based Geographic Information
Systems, often for data interchange. It is a pretty simple
library and it is my first effort at creating such bindings.

https://github.com/craig-dillabaugh/shplib.d

I've looked in Demios and code.dlang.org to see what the standard
setup for such bindings is, and while most are similar there
doesn't seem to be an accepted layout.  If anyone has a moment to
spare I would be happy if someone could have a look to see if
there are any obvious improvements that should be made.

I plan to run a few more tests on my bindings, and once those all
work, I hope to add this to code.dlang.org.


There are only two possible improvements that I can see:

 - The C folder may be better off in the root folder of the project,
   because it doesn't fit with the D sources from a build process point
   of view. In practice it doesn't really hurt either, so your mileage
   may vary.

 - Usually I try to include .lib files for the library bindings on
   Windows, since it greatly simplifies the setup process, which is
   usually trivial on Linux.

Other than that I'd recommend to use a version scheme for the git 
tags/branches that matches the version scheme of the C library (probably 
excluding the patch version, which should be reserved for the binding 
itself). Unfortunately the Deimos bindings use neither branches, nor 
version tags.

Re: DCD 0.3.0-beta1 and DScanner 0.1.0-beta1

[Idan Arye]

On Wednesday, 29 January 2014 at 09:48:55 UTC, fra wrote:

Vim plugin seems to be in a messy state right now.
Completion only works after a dot, and even then it produces
strange output on the dcd-server logging window. Perhaps in 
needs

some update due to changes to the server and client code?


Can you please file an issue report on GitHub? 
(https://github.com/Hackerpilot/DCD/issues)


I don't really want to keep working on the Vim plugins for 
DScanner and DCD. I plan a big plugin sometimes in the near 
feature that will support various D development tools. I will 
want to fetch the list of imports from DUB and feed it to 
DCD\DScanner. I will also want to try DCD first, and if the 
server isn't running revert to DScanner. I can't do those things 
in a plugin that sits in a single tool's repository and is 
dedicated to that tool.


Still - until I do this, fixing bugs is my sacred duty and adding 
support for `--symbolLocation` and `--doc` shouldn't be that much 
work... I'll try to get to it during the weekend.

Re: New debugger for D!!!

[Meta]

Great minds think alike ;-)

On Wednesday, 29 January 2014 at 07:07:25 UTC, Rory McGuire wrote:

+1. Same name I thought of :)


On Wed, Jan 29, 2014 at 2:26 AM, Meta jared...@gmail.com 
wrote:



On Wednesday, 29 January 2014 at 00:07:00 UTC, Namespace wrote:

I did not do any research on name; just shortened debug to 
dbg :)
I'm bad at coming up with good names, so any suggestions are 
always

welcome.

- Sarath



D!buger



Too complicated, keep it simple. Maybe Dug, which stands for D 
Debug.

Re: D bindings for Shapefile C Library

[Craig Dillabaugh]

On Wednesday, 29 January 2014 at 14:09:20 UTC, Gary Willoughby 
wrote:
On Wednesday, 29 January 2014 at 04:24:36 UTC, Craig Dillabaugh 
wrote:

I've created bindings for the C Shapefile Library.  Shapefiles
are a format used commonly in vector based Geographic 
Information

Systems, often for data interchange. It is a pretty simple
library and it is my first effort at creating such bindings.

https://github.com/craig-dillabaugh/shplib.d

I've looked in Demios and code.dlang.org to see what the 
standard

setup for such bindings is, and while most are similar there
doesn't seem to be an accepted layout.  If anyone has a moment 
to

spare I would be happy if someone could have a look to see if
there are any obvious improvements that should be made.

I plan to run a few more tests on my bindings, and once those 
all

work, I hope to add this to code.dlang.org.


This is how i'm doing it:

https://github.com/nomad-software/tcltk

This is a binding for Tcl/Tk libs. I've included windows dll 
import libraries in various formats (for different environments 
and compilers) to make the build process easier. I've also kept 
the c headers in the source folder but excluded them in the 
package.json file (just in case). I've added one version (the 
same as the c sources) for when the bindings supported an older 
version but the latest version is in master.


Thanks. I've had a few requests to generate .lib files so I will 
see about that.  I don't do very much development on Windows, but 
this should be good practice for me.

Re: D bindings for Shapefile C Library

[Gary Willoughby]

A few things i tend to do when porting headers:

1). 
https://github.com/craig-dillabaugh/shplib.d/blob/master/source/shapefil.d#L267


'const char *filename' should usually be translated to 
'const(char)* filename',

'const double * padfX' = 'const(double)* padfX'
etc..

Reference:
http://forum.dlang.org/thread/qvjjzoxoufxnxzoky...@forum.dlang.org

2). 
https://github.com/craig-dillabaugh/shplib.d/blob/master/source/shapefil.d#L275


Underscores on identifiers that match keywords are usually added 
to the end.


Reference:
http://dlang.org/dstyle.html

3). 
https://github.com/craig-dillabaugh/shplib.d/blob/master/source/shapefil.d#L263
longs/ulongs tend to be substituted for c_long/c_ulong from 
core.stdc.config.


Reference:
http://dlang.org/interfaceToC.html

4). 
https://github.com/craig-dillabaugh/shplib.d/blob/master/source/shapefil.d#L721

I tend to add const to all char* types as above.

In general, add 'nothrow' to all functions and move the '*' to be 
part of the type. e.g.:
'const(char)* text' instead of 'const(char) *text', this is my 
own personal preference though. :p

Re: COMPO - 2.064

[bearophile]

Steve Teale:

I pushed changes to GitHub (https://github.com/britseye/compo) 
today that allow a clean build with warnings and deprecations 
on using DMD2.064.


In similar projects I suggest to pull out some generally useful 
modules (like some geometry ones), making them independent, and 
making them available (with DUB or on GitHub). This allows other 
projects to re-use those modules and reduce their size.


Bye,
bearophile

Re: D bindings for Shapefile C Library

[Craig Dillabaugh]

On Wednesday, 29 January 2014 at 14:34:56 UTC, Gary Willoughby 
wrote:

A few things i tend to do when porting headers:

1). 
https://github.com/craig-dillabaugh/shplib.d/blob/master/source/shapefil.d#L267


'const char *filename' should usually be translated to 
'const(char)* filename',

'const double * padfX' = 'const(double)* padfX'
etc..

Reference:
http://forum.dlang.org/thread/qvjjzoxoufxnxzoky...@forum.dlang.org

2). 
https://github.com/craig-dillabaugh/shplib.d/blob/master/source/shapefil.d#L275


Underscores on identifiers that match keywords are usually 
added to the end.


Reference:
http://dlang.org/dstyle.html

3). 
https://github.com/craig-dillabaugh/shplib.d/blob/master/source/shapefil.d#L263
longs/ulongs tend to be substituted for c_long/c_ulong from 
core.stdc.config.


Reference:
http://dlang.org/interfaceToC.html

4). 
https://github.com/craig-dillabaugh/shplib.d/blob/master/source/shapefil.d#L721

I tend to add const to all char* types as above.

In general, add 'nothrow' to all functions and move the '*' to 
be part of the type. e.g.:
'const(char)* text' instead of 'const(char) *text', this is my 
own personal preference though. :p


Thanks very much.

Re: New debugger for D!!!

[John J]

On 01/28/2014 07:26 PM, Meta wrote:

On Wednesday, 29 January 2014 at 00:07:00 UTC, Namespace wrote:

I did not do any research on name; just shortened debug to dbg :)
I'm bad at coming up with good names, so any suggestions are always
welcome.

- Sarath


D!buger


Too complicated, keep it simple. Maybe Dug, which stands for D Debug.



Dug sounds good!

Re: New debugger for D!!!

[Sarath Kodali]

On Wednesday, 29 January 2014 at 07:06:43 UTC, Andrei 
Alexandrescu wrote:

On 1/28/14 4:26 PM, Meta wrote:

On Wednesday, 29 January 2014 at 00:07:00 UTC, Namespace wrote:
I did not do any research on name; just shortened debug to 
dbg :)
I'm bad at coming up with good names, so any suggestions are 
always

welcome.

- Sarath


D!buger


Too complicated, keep it simple. Maybe Dug, which stands for D 
Debug.


noice


http://www.noicedebugger.com/ already exists!

Re: New debugger for D!!!

[Gary Willoughby]

On Wednesday, 29 January 2014 at 16:20:33 UTC, Sarath Kodali 
wrote:
On Wednesday, 29 January 2014 at 07:06:43 UTC, Andrei 
Alexandrescu wrote:

On 1/28/14 4:26 PM, Meta wrote:
On Wednesday, 29 January 2014 at 00:07:00 UTC, Namespace 
wrote:
I did not do any research on name; just shortened debug 
to dbg :)
I'm bad at coming up with good names, so any suggestions 
are always

welcome.

- Sarath


D!buger


Too complicated, keep it simple. Maybe Dug, which stands for 
D Debug.


noice


http://www.noicedebugger.com/ already exists!


I like bugD :o)

Re: New debugger for D!!!

[Andrea Fontana]

On Wednesday, 29 January 2014 at 16:33:47 UTC, Gary Willoughby 
wrote:
On Wednesday, 29 January 2014 at 16:20:33 UTC, Sarath Kodali 
wrote:
On Wednesday, 29 January 2014 at 07:06:43 UTC, Andrei 
Alexandrescu wrote:

On 1/28/14 4:26 PM, Meta wrote:
On Wednesday, 29 January 2014 at 00:07:00 UTC, Namespace 
wrote:
I did not do any research on name; just shortened debug 
to dbg :)
I'm bad at coming up with good names, so any suggestions 
are always

welcome.

- Sarath


D!buger


Too complicated, keep it simple. Maybe Dug, which stands for 
D Debug.


noice


http://www.noicedebugger.com/ already exists!


I like bugD :o)


d-bugger

Re: DCD 0.3.0-beta1 and DScanner 0.1.0-beta1

[Rory McGuire]

DKit and the beta appear to be working nicely on sublime text 2
On 28 Jan 2014 12:02, Brian Schott briancsch...@gmail.com wrote:

 New DCD and DScanner betas are  ready for testing. The tags can be found
 here:

 https://github.com/Hackerpilot/DCD/tree/0.3.0-beta1
 https://github.com/Hackerpilot/Dscanner/tree/0.1.0-beta1

 DCD Changes:
 * Uptake new lexer/parser/ast code from DScanner
 * Add new --symbolLocation switch that instructs the server to return the
   declaration location of the symbol at the cursor
 * Add new --doc switch that instructs the server to return any
 documentation
   comments associated with the symbol at the cursor
 * Fixed #89: Template declarations not included in autocomplete
 * Fixed #88: Fully qualified names not working
 * Fixed #82: Unable to generate calltips for methods called on variables
 * Fixed #79: Unable to build with both DMD and GDC
 * Fixed #75: Vim plugin doesn't work?

 DScanner changes:
 * Now actually tagged with version numbers!
 * Implemented experimental --styleCheck option that will run some basic
   static analysis checks on the files provided.
 ** Warns when opCmp, toHash, toString, and opEquals are not const
 ** Warns on implicit concatenation of string literals
 ** Warns on catching the base exception types (i.e Exception, Throwable,
 etc)
 ** Warns when the deprecated floating-point operators are used
 ** Warns when the deprecated delete keyword is used
 ** Warns when large enum constants such as array literals are created.
 ** Warns when using old-style alias declarations (i.e. alias type
 identifier
instead of alias identifier = type)
 ** Warns when using deprecated complex number literals.
 ** Warns on empty statements (i.e. spare semicolons)
 ** Warns when using large number literals without underscores
 ** Warns on violations of the Phobos naming conventions (e.g. mixed case
package names, lowercase class names, etc)
 * Fixed many issues in the parser
 * Fixed issues with the AST dump not correctly printing several expression
 node
   types
 * Rewrote lexer, parser, and AST code. The new lexer generator should be
 ready
   for another Phobos review very soon.

 About DCD:

 DCD is the D Completion Daemon, a text editor and IDE-neutral
 autocompletion engine for the D programming language. DCD has plugins for
 several editors such as Textadept, Kate, Vim, Emacs, Zeus, and Sublime Text
 3.

 About DScanner:

 DScanner is a Swiss army knife for D source code. It can perform various
 tasks such as
 * Source line of code counting
 * Import listing
 * HTML syntax highlighting
 * Syntax checking
 * Some basic static analysis
 * Generating CTAGS
 * Generating an outline of a D file
 * Dumping the AST of a D file into an XML file.

 P.S. Only the Textadept module has support for the new --symbolLocation
 and --doc switches. If you're one of the excellent people who wrote one of
 the other plugins, I'd appreciate your help adding support for these
 features to your favorite editor before a non-beta release is tagged.

Re: New debugger for D!!!

[Meta]

On Wednesday, 29 January 2014 at 16:45:20 UTC, Andrea Fontana 
wrote:
On Wednesday, 29 January 2014 at 16:33:47 UTC, Gary Willoughby 
wrote:
On Wednesday, 29 January 2014 at 16:20:33 UTC, Sarath Kodali 
wrote:
On Wednesday, 29 January 2014 at 07:06:43 UTC, Andrei 
Alexandrescu wrote:

On 1/28/14 4:26 PM, Meta wrote:
On Wednesday, 29 January 2014 at 00:07:00 UTC, Namespace 
wrote:
I did not do any research on name; just shortened debug 
to dbg :)
I'm bad at coming up with good names, so any suggestions 
are always

welcome.

- Sarath


D!buger


Too complicated, keep it simple. Maybe Dug, which stands 
for D Debug.


noice


http://www.noicedebugger.com/ already exists!


I like bugD :o)


d-bugger


That'll give anyone from the UK a good laugh.

Re: New debugger for D!!!

[Russel Winder]

On Wed, 2014-01-29 at 16:45 +, Andrea Fontana wrote:
[…]
 
 d-bugger

You may want to belay that suggestion:

http://en.wikipedia.org/wiki/Bugger
http://www.thefreedictionary.com/bugger
http://www.oxforddictionaries.com/definition/english/bugger
http://www.urbandictionary.com/define.php?term=bugger

-- 
Russel.
=
Dr Russel Winder  t: +44 20 7585 2200   voip: sip:russel.win...@ekiga.net
41 Buckmaster Roadm: +44 7770 465 077   xmpp: rus...@winder.org.uk
London SW11 1EN, UK   w: www.russel.org.uk  skype: russel_winder

Re: New debugger for D!!!

[Andrei Alexandrescu]

On 1/29/14 8:20 AM, Sarath Kodali wrote:

On Wednesday, 29 January 2014 at 07:06:43 UTC, Andrei Alexandrescu wrote:

On 1/28/14 4:26 PM, Meta wrote:

On Wednesday, 29 January 2014 at 00:07:00 UTC, Namespace wrote:

I did not do any research on name; just shortened debug to dbg :)
I'm bad at coming up with good names, so any suggestions are always
welcome.

- Sarath


D!buger


Too complicated, keep it simple. Maybe Dug, which stands for D Debug.


noice


http://www.noicedebugger.com/ already exists!


noice = nice in Australian, i.e. I meant I like Dug. See also 
http://bostondanceparty.deviantart.com/art/Australia-162070359


Andrei

Re: New debugger for D!!!

[Andrea Fontana]

On Wednesday, 29 January 2014 at 16:55:40 UTC, Meta wrote:
On Wednesday, 29 January 2014 at 16:45:20 UTC, Andrea Fontana 
wrote:
On Wednesday, 29 January 2014 at 16:33:47 UTC, Gary Willoughby 
wrote:
On Wednesday, 29 January 2014 at 16:20:33 UTC, Sarath Kodali 
wrote:
On Wednesday, 29 January 2014 at 07:06:43 UTC, Andrei 
Alexandrescu wrote:

On 1/28/14 4:26 PM, Meta wrote:
On Wednesday, 29 January 2014 at 00:07:00 UTC, Namespace 
wrote:
I did not do any research on name; just shortened 
debug to dbg :)
I'm bad at coming up with good names, so any suggestions 
are always

welcome.

- Sarath


D!buger


Too complicated, keep it simple. Maybe Dug, which stands 
for D Debug.


noice


http://www.noicedebugger.com/ already exists!


I like bugD :o)


d-bugger


That'll give anyone from the UK a good laugh.


:)

Maybe d-bugging works better

Re: New debugger for D!!!

[Russel Winder]

On Wed, 2014-01-29 at 16:55 +, Meta wrote:
 On Wednesday, 29 January 2014 at 16:45:20 UTC, Andrea Fontana 
[…]
  d-bugger
 
 That'll give anyone from the UK a good laugh.

Sort of.

Remember bugger is colloquially a general purpose expletive as well as
being a synonym for sodomy.

-- 
Russel.
=
Dr Russel Winder  t: +44 20 7585 2200   voip: sip:russel.win...@ekiga.net
41 Buckmaster Roadm: +44 7770 465 077   xmpp: rus...@winder.org.uk
London SW11 1EN, UK   w: www.russel.org.uk  skype: russel_winder

Re: New debugger for D!!!

[Justin Whear]

On Wed, 29 Jan 2014 17:03:59 +, Russel Winder wrote:

 On Wed, 2014-01-29 at 16:45 +, Andrea Fontana wrote: […]
 
 d-bugger
 
 You may want to belay that suggestion:
 
 http://en.wikipedia.org/wiki/Bugger
 http://www.thefreedictionary.com/bugger
 http://www.oxforddictionaries.com/definition/english/bugger
 http://www.urbandictionary.com/define.php?term=bugger

bugger-d
Do it for the LOLs

Re: DCD 0.3.0-beta1 and DScanner 0.1.0-beta1

[Brian Schott]

DCD 0.3.0-beta2 has been tagged.

https://github.com/Hackerpilot/DCD/tree/0.3.0-beta2

Changes since last beta:
* Fixed #90: Go to declaration does not work correctly with 
member variables.

* Updated DScanner dependency to fix a parser bug.

Re: DCD 0.3.0-beta1 and DScanner 0.1.0-beta1

[Brian Schott]

On Thursday, 30 January 2014 at 00:26:47 UTC, Jussi Jumppanen 
wrote:

On Tuesday, 28 January 2014 at 09:58:27 UTC, Brian Schott wrote:

New DCD and DScanner betas are ready for testing.


I'm no D expert so I'm not really sure if this is a bug with DCD
or
with the DMD compiler itself? I suspect it might be the later?


https://github.com/Hackerpilot/DCD/issues

Re: DCD 0.3.0-beta1 and DScanner 0.1.0-beta1

[Jussi Jumppanen]

On Tuesday, 28 January 2014 at 09:58:27 UTC, Brian Schott wrote:

New DCD and DScanner betas are ready for testing.


I'm no D expert so I'm not really sure if this is a bug with DCD
or
with the DMD compiler itself? I suspect it might be the later?

I was testing your latest DCD against the Zeus IDE but came across
the following issue when trying to build DCD.

I tried doing the build using the zip files as follows:

1) Download the dmd.2.064.2.zip from here:

http://dlang.org/download.html

2) Download the DCD, DScanner and msgpack source zip files from
these pages:

https://github.com/Hackerpilot/DCD/tree/0.3.0-beta1
https://github.com/Hackerpilot/Dscanner/tree/0.1.0-beta1
https://github.com/msgpack/msgpack-d

When I run the BUILD.BAT the client exe builds just fine but
the build of the server exe hangs.

So I played around with the BUILD.BAT and found the build was
hanging on this file:

dscanner/stdx/d/lexer.d

I then ran this command to just build that one file:

 dmd -v -wi dscanner/stdx/d/lexer.d -Imsgpack-d/src -Idscanner
-O -release -noboundscheck -inline -ofdcd-server.exe

That command gives the compiler trace output shown below.

It appears that the dmd.exe hang on this file with this as the
last
line of trace output:

 TTY_FUNCTION__, __TIME__, __TIMESTAMP__, __traits,
__vector, __VENDOR__, __VERSION__]).advance

The task manager shows the dmd.exe running but just continually
consuming more and more memory.

Compiler Trace Output
-

NOTE: Some excessive trace output trimmed with ... characters.

D:\projects\dcd\DCD-0.3.0-beta2dmd -v -wi
dscanner/stdx/d/lexer.d -Imsgpack-d/src -Idscanner -O -release
-noboundscheck
  -inline -ofdcd-server.exe
binaryc:\dmd2\windows\bin\dmd.exe
version   v2.064
configc:\dmd2\windows\bin\sc.ini
parse lexer
importall lexer
importstd.uni
(c:\dmd2\windows\bin\..\..\src\phobos\std\uni.d)
...
importcore.sys.windows.windows
(c:\dmd2\windows\bin\..\..\src\druntime\import\core\sys\windows\windows.d)
importstdx.lexer(dscanner\stdx\lexer.d)
semantic  lexer
semantic2 lexer
semantic3 lexer
importstd.stdio
(c:\dmd2\windows\bin\..\..\src\phobos\std\stdio.d)
...
importstd.internal.uni_tab
(c:\dmd2\windows\bin\..\..\src\phobos\std\internal\uni_tab.d)
semantic3 lexer
...
semantic3 utf
semantic3 uni
importstd.internal.unicode_comp
(c:\dmd2\windows\bin\..\..\src\phobos\std\internal\unicode_comp.d)
...
importstd.internal.unicode_decomp
(c:\dmd2\windows\bin\..\..\src\phobos\std\internal\unicode_decomp.d)
semantic3 unicode_tables
...
inline scan lexer
code  lexer
function  stdx.d.lexer.LexerConfig.__xopEquals
...
function  stdx.d.lexer.DLexer.Lexer!(ubyte,
TokenStructure!(ubyte, \x0a\x09string comment;\x0a\x0a\x09int
opCmp(size_t
i) const pure nothrow @safe {\x0a\x09\x09if (index  i) return
-1;\x0a\x09\x09if (index  i) return 1;\x0a\x09\x09return
...
with, __DATE__, __EOF__, __FILE__, __FUNCTION__,
__gshared, __LINE__, __MODULE__, __parameters, __PRE
TTY_FUNCTION__, __TIME__, __TIMESTAMP__, __traits,
__vector, __VENDOR__, __VERSION__]).generateMask
function  stdx.d.lexer.DLexer.Lexer!(ubyte,
TokenStructure!(ubyte, \x0a\x09string comment;\x0a\x0a\x09int
opCmp(size_t
i) const pure nothrow @safe {\x0a\x09\x09if (index  i) return
-1;\x0a\x09\x09if (index  i) return 1;\x0a\x09\x09return
...
with, __DATE__, __EOF__, __FILE__, __FUNCTION__,
__gshared, __LINE__, __MODULE__, __parameters, __PRE
TTY_FUNCTION__, __TIME__, __TIMESTAMP__, __traits,
__vector, __VENDOR__, __VERSION__]).generateByteMask
function  stdx.d.lexer.DLexer.Lexer!(ubyte,
TokenStructure!(ubyte, \x0a\x09string comment;\x0a\x0a\x09int
opCmp(size_t
i) const pure nothrow @safe {\x0a\x09\x09if (index  i) return
-1;\x0a\x09\x09if (index  i) return 1;\x0a\x09\x09return
...
of, ubyte, ucent, uint, ulong, union, unittest,
ushort, version, void, volatile, wchar, while,
with, __DATE__, __EOF__, __FILE__, __FUNCTION__,
__gshared, __LINE__, __MODULE__, __parameters, __PRE
TTY_FUNCTION__, __TIME__, __TIMESTAMP__, __traits,
__vector, __VENDOR__, __VERSION__]).generateCaseStatemen
ts
function  stdx.d.lexer.DLexer.Lexer!(ubyte,
TokenStructure!(ubyte, \x0a\x09string comment;\x0a\x0a\x09int
opCmp(size_t
i) const pure nothrow @safe {\x0a\x09\x09if (index  i) return
-1;\x0a\x09\x09if (index  i) return 1;\x0a\x09\x09return
...
with, __DATE__, __EOF__, __FILE__, __FUNCTION__,
__gshared, __LINE__, __MODULE__, __parameters, __PRE
TTY_FUNCTION__, __TIME__, __TIMESTAMP__, __traits,
__vector, __VENDOR__, __VERSION__]).printCase
function  stdx.d.lexer.DLexer.Lexer!(ubyte,
TokenStructure!(ubyte, \x0a\x09string comment;\x0a\x0a\x09int
opCmp(size_t
i) const pure nothrow @safe {\x0a\x09\x09if (index  i) return
-1;\x0a\x09\x09if (index  i) return 1;\x0a\x09\x09return
...
with, __DATE__, __EOF__, __FILE__, __FUNCTION__,
__gshared, __LINE__, __MODULE__, __parameters, __PRE
TTY_FUNCTION__, __TIME__, __TIMESTAMP__, __traits,
__vector, __VENDOR__, __VERSION__]).front
function  

Re: DCD 0.3.0-beta1 and DScanner 0.1.0-beta1

[Jussi Jumppanen]

Created this issue:

https://github.com/Hackerpilot/DCD/issues/93

Re: D bindings for Shapefile C Library

[Craig Dillabaugh]

On Wednesday, 29 January 2014 at 05:26:31 UTC, Suliman wrote:
Big thanks! Could you provide simple example of usage this lib. 
I
have not experience in usage bindings, but I would like to try 
to

write some tiny app to working with shp files.


Not sure what sort of help you need, and what platform?

First thing I would suggest though is to get your hands on some 
Shapefile data.  You can get some free stuff here (there is lots 
of free Shapefile data floating around out there):


http://download.geofabrik.de/

Note that a Shapefile is actually a collection of files (.shp, 
.shx, .dbf, .prj) sharing the same base name. You need all the 
files in the same location and then if you access 'building' the 
library will need the files building.shp, building.shx, 
building.dbf (I think the .prj is optional).


To actually build The Shapefile library you can download it form 
here:


http://shapelib.maptools.org/

I build an static library on linux ( libshp.a ) and then, because 
I was lazy and libshp is small I just copied that into my test 
directory and built a test program with the following command:


dmd -gc shapetest.d shapefil.d libshp.a

Where shapetest.d is my test program, shapefil.d is my binding, 
and libshp.a is the library.


My shapetest.d is currently a bit of a mess, but I can put it on 
gitHub in a day or two if you would like.

Re: DCD 0.3.0-beta1 and DScanner 0.1.0-beta1

[Rory McGuire]

Could you try build with the dmd beta?
On 30 Jan 2014 02:30, Jussi Jumppanen jus...@zeusedit.com wrote:

 On Tuesday, 28 January 2014 at 09:58:27 UTC, Brian Schott wrote:

 New DCD and DScanner betas are ready for testing.


 I'm no D expert so I'm not really sure if this is a bug with DCD
 or
 with the DMD compiler itself? I suspect it might be the later?

 I was testing your latest DCD against the Zeus IDE but came across
 the following issue when trying to build DCD.

 I tried doing the build using the zip files as follows:

 1) Download the dmd.2.064.2.zip from here:

 http://dlang.org/download.html

 2) Download the DCD, DScanner and msgpack source zip files from
 these pages:

 https://github.com/Hackerpilot/DCD/tree/0.3.0-beta1
 https://github.com/Hackerpilot/Dscanner/tree/0.1.0-beta1
 https://github.com/msgpack/msgpack-d

 When I run the BUILD.BAT the client exe builds just fine but
 the build of the server exe hangs.

 So I played around with the BUILD.BAT and found the build was
 hanging on this file:

 dscanner/stdx/d/lexer.d

 I then ran this command to just build that one file:

  dmd -v -wi dscanner/stdx/d/lexer.d -Imsgpack-d/src -Idscanner
 -O -release -noboundscheck -inline -ofdcd-server.exe

 That command gives the compiler trace output shown below.

 It appears that the dmd.exe hang on this file with this as the
 last
 line of trace output:

  TTY_FUNCTION__, __TIME__, __TIMESTAMP__, __traits,
 __vector, __VENDOR__, __VERSION__]).advance

 The task manager shows the dmd.exe running but just continually
 consuming more and more memory.

 Compiler Trace Output
 -

 NOTE: Some excessive trace output trimmed with ... characters.

 D:\projects\dcd\DCD-0.3.0-beta2dmd -v -wi
 dscanner/stdx/d/lexer.d -Imsgpack-d/src -Idscanner -O -release
 -noboundscheck
   -inline -ofdcd-server.exe
 binaryc:\dmd2\windows\bin\dmd.exe
 version   v2.064
 configc:\dmd2\windows\bin\sc.ini
 parse lexer
 importall lexer
 importstd.uni
 (c:\dmd2\windows\bin\..\..\src\phobos\std\uni.d)
 ...
 importcore.sys.windows.windows
 (c:\dmd2\windows\bin\..\..\src\druntime\import\core\sys\windows\windows.d)
 importstdx.lexer(dscanner\stdx\lexer.d)
 semantic  lexer
 semantic2 lexer
 semantic3 lexer
 importstd.stdio
 (c:\dmd2\windows\bin\..\..\src\phobos\std\stdio.d)
 ...
 importstd.internal.uni_tab
 (c:\dmd2\windows\bin\..\..\src\phobos\std\internal\uni_tab.d)
 semantic3 lexer
 ...
 semantic3 utf
 semantic3 uni
 importstd.internal.unicode_comp
 (c:\dmd2\windows\bin\..\..\src\phobos\std\internal\unicode_comp.d)
 ...
 importstd.internal.unicode_decomp
 (c:\dmd2\windows\bin\..\..\src\phobos\std\internal\unicode_decomp.d)
 semantic3 unicode_tables
 ...
 inline scan lexer
 code  lexer
 function  stdx.d.lexer.LexerConfig.__xopEquals
 ...
 function  stdx.d.lexer.DLexer.Lexer!(ubyte,
 TokenStructure!(ubyte, \x0a\x09string comment;\x0a\x0a\x09int
 opCmp(size_t
 i) const pure nothrow @safe {\x0a\x09\x09if (index  i) return
 -1;\x0a\x09\x09if (index  i) return 1;\x0a\x09\x09return
 ...
 with, __DATE__, __EOF__, __FILE__, __FUNCTION__,
 __gshared, __LINE__, __MODULE__, __parameters, __PRE
 TTY_FUNCTION__, __TIME__, __TIMESTAMP__, __traits,
 __vector, __VENDOR__, __VERSION__]).generateMask
 function  stdx.d.lexer.DLexer.Lexer!(ubyte,
 TokenStructure!(ubyte, \x0a\x09string comment;\x0a\x0a\x09int
 opCmp(size_t
 i) const pure nothrow @safe {\x0a\x09\x09if (index  i) return
 -1;\x0a\x09\x09if (index  i) return 1;\x0a\x09\x09return
 ...
 with, __DATE__, __EOF__, __FILE__, __FUNCTION__,
 __gshared, __LINE__, __MODULE__, __parameters, __PRE
 TTY_FUNCTION__, __TIME__, __TIMESTAMP__, __traits,
 __vector, __VENDOR__, __VERSION__]).generateByteMask
 function  stdx.d.lexer.DLexer.Lexer!(ubyte,
 TokenStructure!(ubyte, \x0a\x09string comment;\x0a\x0a\x09int
 opCmp(size_t
 i) const pure nothrow @safe {\x0a\x09\x09if (index  i) return
 -1;\x0a\x09\x09if (index  i) return 1;\x0a\x09\x09return
 ...
 of, ubyte, ucent, uint, ulong, union, unittest,
 ushort, version, void, volatile, wchar, while,
 with, __DATE__, __EOF__, __FILE__, __FUNCTION__,
 __gshared, __LINE__, __MODULE__, __parameters, __PRE
 TTY_FUNCTION__, __TIME__, __TIMESTAMP__, __traits,
 __vector, __VENDOR__, __VERSION__]).generateCaseStatemen
 ts
 function  stdx.d.lexer.DLexer.Lexer!(ubyte,
 TokenStructure!(ubyte, \x0a\x09string comment;\x0a\x0a\x09int
 opCmp(size_t
 i) const pure nothrow @safe {\x0a\x09\x09if (index  i) return
 -1;\x0a\x09\x09if (index  i) return 1;\x0a\x09\x09return
 ...
 with, __DATE__, __EOF__, __FILE__, __FUNCTION__,
 __gshared, __LINE__, __MODULE__, __parameters, __PRE
 TTY_FUNCTION__, __TIME__, __TIMESTAMP__, __traits,
 __vector, __VENDOR__, __VERSION__]).printCase
 function  stdx.d.lexer.DLexer.Lexer!(ubyte,
 TokenStructure!(ubyte, \x0a\x09string comment;\x0a\x0a\x09int
 opCmp(size_t
 i) const pure nothrow @safe {\x0a\x09\x09if (index  i) return
 -1;\x0a\x09\x09if (index  i) return