On Tuesday, 24 January 2012 at 16:09:21 UTC, Artur Skawina wrote:
So instead of:
gdk_rectangle_union(dirtyRect, event.area, dirtyRect);
you can write:
dirtyRect.union_(event.area, dirtyRect);
For some reason
gdk_rectangle_union(dirtyRect, event.area, dirtyRect);
looks better.
and all
On 01/28/12 17:28, Kagamin wrote:
On Tuesday, 24 January 2012 at 16:09:21 UTC, Artur Skawina wrote:
and all of these will result in identical code being emitted.
what if
struct Rectangle
{
GdkRectangle r;
alias r this;
... methods ...
}
Will a different code be emitted?
Will alias
On Sunday, 22 January 2012 at 21:56:24 UTC, Artur Skawina wrote:
Native GTK2 bindings for D.
Native for two reasons:
1. Uses the C API directly. No class wrappers and no function
wrappers.
2. OO interface, giving a native D look and feel.
Once again. Is it direct C
On 01/24/12 12:15, Kagamin wrote:
On Sunday, 22 January 2012 at 21:56:24 UTC, Artur Skawina wrote:
Native GTK2 bindings for D.
Native for two reasons:
1. Uses the C API directly. No class wrappers and no function wrappers.
2. OO interface, giving a native D look and
On 2012-01-24 17:09, Artur Skawina wrote:
On 01/24/12 12:15, Kagamin wrote:
On Sunday, 22 January 2012 at 21:56:24 UTC, Artur Skawina wrote:
Native GTK2 bindings for D.
Native for two reasons:
1. Uses the C API directly. No class wrappers and no function wrappers.
2. OO
On Tue, 24 Jan 2012 21:03:22 +0100
Jacob Carlborg d...@me.com wrote:
So what's the difference compared to gtkD:
I believe it was already mentioned: NIH syndrome. ;)
Sincerely,
Gour
--
Those persons who execute their duties according to My injunctions
and who follow this teaching
On 01/24/12 21:03, Jacob Carlborg wrote:
On 2012-01-24 17:09, Artur Skawina wrote:
On 01/24/12 12:15, Kagamin wrote:
On Sunday, 22 January 2012 at 21:56:24 UTC, Artur Skawina wrote:
Native GTK2 bindings for D.
Native for two reasons:
1. Uses the C API directly. No
Artur Skawina:
There is no such thing as a language mandated identifier naming convention.
If you think otherwise - make the compiler enforce it. :)
There is a D style guide.
This line of code seems an example for people that like named arguments in
D:
gtk.init(null,null);
This has
On 01/24/2012 12:18 AM, bearophile wrote:
Artur Skawina:
There is no such thing as a language mandated identifier naming convention.
If you think otherwise - make the compiler enforce it. :)
There is a D style guide.
This line of code seems an example for people that like named arguments
The function names should be converted to camelCase.
and a README.
gdc does cross module inlining if you pass all modules to it at once.
On 01/23/12 00:16, Trass3r wrote:
The function names should be converted to camelCase.
No. I named it native for a reason. The method names are not manipulated
in any way - they come directly from GTK.
I could *add* all kind of aliases, including camelCased ones, but why would
anyone want to
No. I named it native for a reason. The method names are not
manipulated in any way - they come directly from GTK.
I could *add* all kind of aliases, including camelCased ones, but why
would anyone want to use those?
Cause those C names with underscores are just crappy.
gdc does cross
Artur Skawina:
So far, a sample D GTK app looks like this:
http://repo.or.cz/w/girtod.git/blob/refs/heads/master:/example_gtk3.d
Anything I could change API-wise to improve things, that doesn't
require language changes?
The convention for D classes/structs/enums is CamelCase, while
On 01/23/12 03:17, bearophile wrote:
Artur Skawina:
So far, a sample D GTK app looks like this:
http://repo.or.cz/w/girtod.git/blob/refs/heads/master:/example_gtk3.d
Anything I could change API-wise to improve things, that doesn't
require language changes?
The convention for D
14 matches
Mail list logo
