Re: Release D 2.077.0

[Nick Sabalausky (Abscissa) via Digitalmars-d-announce]

On 11/02/2017 06:35 PM, Martin Nowak wrote:

reproducible dmd builds,


Curiosity: What exactly was preventing this before? Order of source 
files altering the order of output? Something else?


Also, just musing...Regarding the matter of __TIME__(etc) breaking this 
guarantee (breaking it for obvious reasons). Seems to me it would be 
helpful to have compiler switches to force lexer symbols to specific 
values in order to bring at least some level of reproducablity even to 
projects that do use such symbols.

Re: New version of JavacTo available.

[rikki cattermole via Digitalmars-d-announce]

On 03/11/2017 12:17 AM, Patrick wrote:

Please to announce:

A new version of JavacTo available for download. Version 1.1
https://sourceforge.net/projects/javacto/


Features:
* Updated JavacToD visitor. Almost 100% parsing success with dscanner 
and JDK package subset (see results below).


* Updated JavacToJava visitor.

* Source and Target Text pane mouse click integration with List and Tree 
views. Click in a text pane and the list and tree view will update with 
the related visitor node. Very cool.


* New search capabilities. Text and Tree.Kind search.

* Support for command line translation (non-UI, very fast).

* Target highlighting is now automatic (matches java source 
highlighting). No need to add code to highlight. In fact, manually 
highlighting code is discouraged.


* Process dialog when reading large .zip/.jar files.

* Other UI enhancements.


Results with dscanner:
Package  Total files   Failed
java.util    362    15
java.math    8    1
java.net    78    0
java.nio    126    1
java.io    83    0
java.lang    219    4

Success is attributed to dscanner providing no output when parsing a file.

Failures are all attributed error output from:
* Java’s hybrid enum definition. (Which I believe will take a D enum and 
custom class to implement.)

* Java’s lambda method definition.

Successful parsing with dscanner I believe is a major milestone for 
JavacTo. This suggests a good percentage of java code can be 
automatically translated to D. Clearly this is not a definitive 
statement just yet, but an encouraging move in the right direction. 
Dscanner can now be used to format the JavacToD generated code for code 
review. And  critique the quality of the code generated (or 
worse, the quality of the java code :).


It’s clear the next step is to successfully compile the code. With 
effort working towards a successful compile, there's no doubt more 
changes are in store for the JavacToD visitor code. In addition, I’m 
anticipating some hand editing of the generated code will be required 
while other code will be thrown out. Perhaps helper code will be 
warranted as well. In any case, we'll see where the compiler takes us as 
we work towards a weighted balance of auto-generated code to hand 
editing.  Anyway, to be clear, the current objective (hope) is to create 
a D library based on java JDK subset listed above (or something close to 
it). This library can then be used as the bases for translating other 
open source java projects to D.


So… more work to be done.

Patrick


Could you instead side-track and create JNI bindings instead?
This would be a massive help for Android.

New version of JavacTo available.

[Patrick via Digitalmars-d-announce]

Please to announce: 

A new version of JavacTo available for download. Version 1.1
https://sourceforge.net/projects/javacto/


Features:
* Updated JavacToD visitor. Almost 100% parsing success with 
dscanner and JDK package subset (see results below).


* Updated JavacToJava visitor.

* Source and Target Text pane mouse click integration with List 
and Tree views. Click in a text pane and the list and tree view 
will update with the related visitor node. Very cool.


* New search capabilities. Text and Tree.Kind search.

* Support for command line translation (non-UI, very fast).

* Target highlighting is now automatic (matches java source 
highlighting). No need to add code to highlight. In fact, 
manually highlighting code is discouraged.


* Process dialog when reading large .zip/.jar files.

* Other UI enhancements.


Results with dscanner:
Package  Total files   Failed
java.util   362 15
java.math   8   1
java.net78  0
java.nio126 1
java.io 83  0
java.lang   219 4

Success is attributed to dscanner providing no output when 
parsing a file.


Failures are all attributed error output from:
* Java’s hybrid enum definition. (Which I believe will take a D 
enum and custom class to implement.)

* Java’s lambda method definition.

Successful parsing with dscanner I believe is a major milestone 
for JavacTo. This suggests a good percentage of java code can be 
automatically translated to D. Clearly this is not a definitive 
statement just yet, but an encouraging move in the right 
direction. Dscanner can now be used to format the JavacToD 
generated code for code review. And  critique the quality 
of the code generated (or worse, the quality of the java code :).


It’s clear the next step is to successfully compile the code. 
With effort working towards a successful compile, there's no 
doubt more changes are in store for the JavacToD visitor code. In 
addition, I’m anticipating some hand editing of the generated 
code will be required while other code will be thrown out. 
Perhaps helper code will be warranted as well. In any case, we'll 
see where the compiler takes us as we work towards a weighted 
balance of auto-generated code to hand editing.  Anyway, to be 
clear, the current objective (hope) is to create a D library 
based on java JDK subset listed above (or something close to it). 
This library can then be used as the bases for translating other 
open source java projects to D.


So… more work to be done.

Patrick

Re: Diamond MVC / Template Engine - v2.1.0 Released

[WebFreak001 via Digitalmars-d-announce]

On Thursday, 19 October 2017 at 23:29:57 UTC, bauss wrote:

I'm pleased to announce that I have just released Diamond 2.1.0.

There has been a lot of updating to Diamond since last 
announced release.


[...]


Looks really useful, how about making a longer example and 
provide a template project? I could also include that template 
project in the code-d project creation dialog

Release D 2.077.0

[Martin Nowak via Digitalmars-d-announce]

Glad to announce D 2.077.0.

This release comes with a new, more compact mangling, templated 
vector operations, reproducible dmd builds, and various fixes.

Thanks to everyone involved in this .

http://downloads.dlang.org/releases/2.x/2.077.0/
http://dlang.org/changelog/2.077.0.html
The dlang.org website will get updated soon.

-Martin

Re: SublimeLinter-contrib-dmd: dmd feedback as you type

[Bastiaan Veelo via Digitalmars-d-announce]

On Thursday, 2 November 2017 at 15:53:08 UTC, Suliman wrote:

On Thursday, 2 November 2017 at 15:28:36 UTC, Suliman wrote:

I install Sublime Linter first and then this linter and error:
Unable to open /C/Users/suliman/AppData/Roaming/Sublime Text 
3/Packages/User/SublimeLinter.sublime-settings


is gone. But issue with auto-completion is still exists.


Oh, my bad. it's Linter but not auto-completion tool. Really 
sorry.


Correct. You can get tool tips by going to 
Tools->sublimeLinter->Open Settings and change to

"tooltips": true,

in the right hand side pane.

Re: SublimeLinter-contrib-dmd: dmd feedback as you type

[Suliman via Digitalmars-d-announce]

On Thursday, 2 November 2017 at 15:28:36 UTC, Suliman wrote:

I install Sublime Linter first and then this linter and error:
Unable to open /C/Users/suliman/AppData/Roaming/Sublime Text 
3/Packages/User/SublimeLinter.sublime-settings


is gone. But issue with auto-completion is still exists.


Oh, my bad. it's Linter but not auto-completion tool. Really 
sorry.

Re: SublimeLinter-contrib-dmd: dmd feedback as you type

[Suliman via Digitalmars-d-announce]

I install Sublime Linter first and then this linter and error:
Unable to open /C/Users/suliman/AppData/Roaming/Sublime Text 
3/Packages/User/SublimeLinter.sublime-settings


is gone. But issue with auto-completion is still exists.

Re: SublimeLinter-contrib-dmd: dmd feedback as you type

[Suliman via Digitalmars-d-announce]

it's seems that it is work, at last it show red labels on code, 
but for example it is do not show right auto completion after 
point in `std.`

https://snag.gy/uP6Uxl.jpg

Re: SublimeLinter-contrib-dmd: dmd feedback as you type

[Suliman via Digitalmars-d-announce]

On Thursday, 2 November 2017 at 15:13:31 UTC, Suliman wrote:
On Thursday, 2 November 2017 at 10:04:44 UTC, Bastiaan Veelo 
wrote:

On Thursday, 2 November 2017 at 10:00:25 UTC, Temtaime wrote:

Support for dub will be great :)

Yes...


Now all works
Thanks !


Alright :-)


Could you write more detail installation instruction?
Do I need only SublimeLinter and your plugin, or I need 
something more? Like tool-tips plugin? Which paths and in which 
menu should I edit?


I am getting error:

Package Control: No updated packages
Unable to open /C/Users/suliman/AppData/Roaming/Sublime Text 
3/Packages/User/SublimeLinter.sublime-settings

Re: SublimeLinter-contrib-dmd: dmd feedback as you type

[Suliman via Digitalmars-d-announce]

On Thursday, 2 November 2017 at 10:04:44 UTC, Bastiaan Veelo 
wrote:

On Thursday, 2 November 2017 at 10:00:25 UTC, Temtaime wrote:

Support for dub will be great :)

Yes...


Now all works
Thanks !


Alright :-)


Could you write more detail installation instruction?
Do I need only SublimeLinter and your plugin, or I need something 
more? Like tool-tips plugin? Which paths and in which menu should 
I edit?

Re: SublimeLinter-contrib-dmd: dmd feedback as you type

[Bastiaan Veelo via Digitalmars-d-announce]

On Thursday, 2 November 2017 at 10:00:25 UTC, Temtaime wrote:

Support for dub will be great :)

Yes...


Now all works
Thanks !


Alright :-)

Re: SublimeLinter-contrib-dmd: dmd feedback as you type

[Temtaime via Digitalmars-d-announce]

On Thursday, 2 November 2017 at 09:43:11 UTC, Bastiaan Veelo 
wrote:
On Thursday, 2 November 2017 at 09:26:48 UTC, Bastiaan Veelo 
wrote:
Does dmd give the error message you expect when you call dmd 
on that particular file by hand? The linter uses these command 
line switches: -o- -w -wi -vcolumns.


How long does that take? Could be timeout...


Takes about 3s to compile single file.

Sorry, figured out an error : missed some include path for dub 
package.

Support for dub will be great :)

Now all works
Thanks !

Re: SublimeLinter-contrib-dmd: dmd feedback as you type

[Bastiaan Veelo via Digitalmars-d-announce]

On Thursday, 2 November 2017 at 09:26:48 UTC, Bastiaan Veelo 
wrote:
Does dmd give the error message you expect when you call dmd on 
that particular file by hand? The linter uses these command 
line switches: -o- -w -wi -vcolumns.


How long does that take? Could be timeout...

Re: SublimeLinter-contrib-dmd: dmd feedback as you type

[Bastiaan Veelo via Digitalmars-d-announce]

On Thursday, 2 November 2017 at 08:35:08 UTC, Temtaime wrote:
On Thursday, 2 November 2017 at 06:43:36 UTC, Bastiaan Veelo 
wrote:

On Wednesday, 1 November 2017 at 20:09:02 UTC, Temtaime wrote:

Works too strange.
Seems it checks only syntax and doesn't display non-syntax 
related errors.


Also, what is your compiler version, OS, and do you have other 
plugins active?


No way to post a reduced example.
I tried it with one-file test example and it displays all the 
errors correctly, but in my projects with 30 KLOCS it displays 
only syntax erorrs.


DMD from git master branch, windows, no other plugins.


Maybe the error is actually detected but shown in a different 
location? Use Tools->SublimeLinter->Show All Errors to see if it 
is there.


You can turn on debugging from the menu 
Tools->SublimeLinter->Debug Mode, and open the console (Ctrl+` or 
icon in lower left corner) to see the dmd output. Do you see the 
error messages you expect?
The linter calls dmd on just the file that is in your view (in a 
temp directory). That is probably not how you compile your 
30KLOCS project, maybe errors depend on that? Does dmd give the 
error message you expect when you call dmd on that particular 
file by hand? The linter uses these command line switches: -o- -w 
-wi -vcolumns.


If there is a difference in what dmd produces and what is picked 
up by the linter, we should adjust the python regex [1]. Note 
that it should discard tracebacks like "called from here". I used 
[5] to help with that. If you want to hack on it yourself, you 
can remove the package SublimeLinter-contrib-dmd and clone [2] 
into C:\Users\\AppData\Roaming\Sublime Text 3\Packages. 
Maybe dmd sends some of its output to stdout. Change [3] from 
util.STREAM_STDERR to util.STREAM_BOTH to make it read from both 
streams.


Does it help setting the linter working directory [4]? Note that 
currently the regex relies on the substring "SublimeLinter3" 
being present in the path to the temp file, I am unsure whether 
that would still work then.


[1] 
https://github.com/veelo/SublimeLinter-contrib-dmd/blob/e2b4270c2318381eb113620631e93de2b18d436e/linter.py#L24-L33

[2] https://github.com/veelo/SublimeLinter-contrib-dmd
[3] 
https://github.com/veelo/SublimeLinter-contrib-dmd/blob/e2b4270c2318381eb113620631e93de2b18d436e/linter.py#L37
[4] 
http://www.sublimelinter.com/en/latest/linter_settings.html?highlight=working#chdir

[5] https://regex101.com/, select python flavor.

Re: Release Candidate [was: Re: Beta 2.077.0]

[Basile B. via Digitalmars-d-announce]

On Monday, 30 October 2017 at 11:12:29 UTC, Basile B. wrote:
On Saturday, 28 October 2017 at 23:21:56 UTC, Martin Nowak 
wrote:

First release candidate for 2.077.0.

The OMF Windows API import libraries were updated, a bug in 
std.bigint was fixed, and the version identifier for 
`-betterC` is now `D_BetterC`.


- -Martin


Thanks, i have no problem here with the RC, tested it well, 
though looking at the log there would be no reason why i would 
have.


Actually there's a REG  :/

a 192 bytes leak is created by the GC, just with an empty main.
Also i don't know how this is possible but travisCI runs with DMD 
2.077 by default (even if not released).

Re: SublimeLinter-contrib-dmd: dmd feedback as you type

[Temtaime via Digitalmars-d-announce]

On Thursday, 2 November 2017 at 06:43:36 UTC, Bastiaan Veelo 
wrote:

On Wednesday, 1 November 2017 at 20:09:02 UTC, Temtaime wrote:

Works too strange.
Seems it checks only syntax and doesn't display non-syntax 
related errors.


Also, what is your compiler version, OS, and do you have other 
plugins active?


No way to post a reduced example.
I tried it with one-file test example and it displays all the 
errors correctly, but in my projects with 30 KLOCS it displays 
only syntax erorrs.


DMD from git master branch, windows, no other plugins.

Re: SublimeLinter-contrib-dmd: dmd feedback as you type

[Bastiaan Veelo via Digitalmars-d-announce]

On Wednesday, 1 November 2017 at 20:09:02 UTC, Temtaime wrote:

Works too strange.
Seems it checks only syntax and doesn't display non-syntax 
related errors.


Also, what is your compiler version, OS, and do you have other 
plugins active?