On Tuesday, 22 January 2013 at 03:00:59 UTC, deadalnix wrote:
The sane option are either to acknowledge that code is in a
text file and choose syntax construct that make it readable
(python) or decorrelate the presentation of the code from its
actual form in the file and use a formatted.
Out
On Wednesday, 16 January 2013 at 15:55:09 UTC, renoX wrote:
On Tuesday, 15 January 2013 at 13:43:12 UTC, Chris wrote:
On Tuesday, 15 January 2013 at 12:36:42 UTC, bearophile wrote:
Chris:
Nested for loops with if-statements can be hard on the eye
in Python, because you have to go back an
Am 21.01.2013, 15:42 Uhr, schrieb Chris wend...@tcd.ie:
As has been said many times before, it should not be the language's job
to enforce indentation. This should be handled by customizable code
editors. Any programmer in his/her right mind will use indentation. So
why enforce it through
On Tue, 15 Jan 2013 20:06:05 -, Walter Bright
newshou...@digitalmars.com wrote:
On 1/15/2013 4:09 AM, bearophile wrote:
One common indentation-related bug is caused by relying on the
indentation to
understand code, while the curly brace language compiler ignores what
you were
seeing
On Tuesday, 15 January 2013 at 06:30:33 UTC, Rob T wrote:
A really important advantage that scripting languages provides
that D does not currently provide, is direct runtime
interpretation of the language. This is very important for the
use cases of script languages such as Ruby and PHP,
Chris:
or indentation (t)errors (Python)
In practice Python usually decreases the number of
indentation-related bugs, even considering the dangling else
warning we have added to D, because indentation and block nesting
are the same thing, it's more DRY :-)
Bye,
bearophile
On Tuesday, 15 January 2013 at 11:00:29 UTC, bearophile wrote:
Chris:
or indentation (t)errors (Python)
In practice Python usually decreases the number of
indentation-related bugs, even considering the dangling else
warning we have added to D, because indentation and block
nesting are the
Maybe it does, but it's annoying while you are writing it, and to be
honest, indentation bugs are far and few between, in my experience, if
you use the curly braces consistently. Only you have more freedom. What
I was referring to was the annoying Python message Wrong indentation in
line ...,
On 01/15/2013 05:00 AM, bearophile wrote:
Chris:
or indentation (t)errors (Python)
In practice Python usually decreases the number of indentation-related
bugs,
Thats so funny I forgot to laugh.
1100110:
Thats so funny I forgot to laugh.
One common indentation-related bug is caused by relying on the
indentation to understand code, while the curly brace language
compiler ignores what you were seeing and only sees the braces. I
have seen many cases of delayed code understanding
On Tuesday, 15 January 2013 at 11:43:58 UTC, David wrote:
Stereotypes of people who never actually used it, other than
tried it
and gave up because they didn't configure their editor
correctly and
blaming python for it. I bet my last indentation error was more
than two
years ago.
Not a
On Tuesday, 15 January 2013 at 12:09:21 UTC, bearophile wrote:
1100110:
Thats so funny I forgot to laugh.
One common indentation-related bug is caused by relying on the
indentation to understand code, while the curly brace language
compiler ignores what you were seeing and only sees the
Am 15.01.2013 13:23, schrieb David:
That's not my experience. Nested for loops with if-statements can be
hard on the eye in Python, because you have to go back an double check
on which level you actually are and the fact that one missing white
space (a typo after deleting a line) screws up the
That's not my experience. Nested for loops with if-statements can be
hard on the eye in Python, because you have to go back an double check
on which level you actually are and the fact that one missing white
space (a typo after deleting a line) screws up the whole script is just
annoying. The
On Tuesday, 15 January 2013 at 12:36:42 UTC, bearophile wrote:
Chris:
Nested for loops with if-statements can be hard on the eye in
Python, because you have to go back an double check on which
level you actually are
If you use the standard 4 spaces indentations and you don't
have ten
On Tuesday, 15 January 2013 at 12:36:42 UTC, bearophile wrote:
Chris:
Nested for loops with if-statements can be hard on the eye in
Python, because you have to go back an double check on which
level you actually are
If you use the standard 4 spaces indentations and you don't
have ten
On Tuesday, 15 January 2013 at 13:43:12 UTC, Chris wrote:
On Tuesday, 15 January 2013 at 12:36:42 UTC, bearophile wrote:
Chris:
Nested for loops with if-statements can be hard on the eye in
Python, because you have to go back an double check on which
level you actually are
If you use the
On 1/14/2013 10:30 PM, Rob T wrote:
A really important advantage that scripting languages provides that D does not
currently provide, is direct runtime interpretation of the language. This is
very important for the use cases of script languages such as Ruby and PHP,
because often they are used
On 1/15/2013 8:37 AM, Paulo Pinto wrote:
Then I started working in multi-site projects with developers from all types of
backgrounds, and understood the value of a consistent project code formatting.
I agree with the value as you say, but as I posted previously I think consistent
formatting
On 1/15/2013 4:09 AM, bearophile wrote:
One common indentation-related bug is caused by relying on the indentation to
understand code, while the curly brace language compiler ignores what you were
seeing and only sees the braces. I have seen many cases of delayed code
understanding caused by
On Tuesday, 15 January 2013 at 20:07:49 UTC, Walter Bright wrote:
On 1/15/2013 8:37 AM, Paulo Pinto wrote:
Then I started working in multi-site projects with developers
from all types of
backgrounds, and understood the value of a consistent project
code formatting.
I agree with the value as
On Tuesday, 15 January 2013 at 20:02:58 UTC, Walter Bright wrote:
On 1/14/2013 10:30 PM, Rob T wrote:
A really important advantage that scripting languages provides
that D does not
currently provide, is direct runtime interpretation of the
language. This is
very important for the use cases of
On Monday, 7 January 2013 at 22:21:59 UTC, Chris wrote:
Another thing, IMO, is that there is an overemphasis on C++ vs.
D. Usually people have to choose between systems programming
(learn C/C++) or high level (learn Python, Ruby etc.). Most
non-programmers who need to write a piece of software
On Sunday, 13 January 2013 at 16:00:27 UTC, SomeDude wrote:
On Monday, 7 January 2013 at 12:16:04 UTC, thedeemon wrote:
On Monday, 7 January 2013 at 11:31:46 UTC, bearophile wrote:
There is also Rust.
I had the impression that Rust was at embryonic stage where it
changes all the time,
On Monday, 7 January 2013 at 12:16:04 UTC, thedeemon wrote:
On Monday, 7 January 2013 at 11:31:46 UTC, bearophile wrote:
There is also Rust.
I had the impression that Rust was at embryonic stage where it
changes all the time, can't really live by itself and is not
born yet. It's an
On Monday, 7 January 2013 at 22:14:46 UTC, Ali Çehreli wrote:
On 01/07/2013 01:57 PM, Phil Lavoie wrote:
I meant scope objects work fine in most cases, but sometimes
its good to
explicitly delete objects on the heap.
Usually, what is needed is to just finalize the object. The
memory that it
Walter Bright:
http://fgda.pl/post/8/a-look-at-the-d-programming-language
From the article:
if you only count the natively-compiled ones that could be used
instead of C++ and have a similarly looking code. D is the best
fit in this category, if not the only fit.1
There is also Rust.
if
On 2013-01-07 11:31:45 +, bearophile said:
Walter Bright:
http://fgda.pl/post/8/a-look-at-the-d-programming-language
From the article:
if you only count the natively-compiled ones that could be used
instead of C++ and have a similarly looking code. D is the best
fit in this category,
On Monday, 7 January 2013 at 11:48:36 UTC, Max Klyga wrote:
On 2013-01-07 11:31:45 +, bearophile said:
Walter Bright:
http://fgda.pl/post/8/a-look-at-the-d-programming-language
From the article:
if you only count the natively-compiled ones that could be
used
instead of C++ and have a
On Monday, 7 January 2013 at 11:31:46 UTC, bearophile wrote:
There is also Rust.
I had the impression that Rust was at embryonic stage where it
changes all the time, can't really live by itself and is not born
yet. It's an interesting project but not a language one would use
today for real
On 2013-01-07 09:32:30 +, Walter Bright said:
http://fgda.pl/post/8/a-look-at-the-d-programming-language
Now on Reddit:
http://www.reddit.com/r/programming/comments/1647y1/a_look_at_the_d_programming_language_by_ferdynand/
On 2013-01-07 11:55:59 +, nazriel said:
snip...
I don't think he has any bad intention, just trying to make core
developers focus on the biggest issues (GC, Shared libraries,
Allocators :).
Guessing at number of bugs reported by Bugophile he is on our side
; And has some good
On Monday, 7 January 2013 at 12:26:12 UTC, Max Klyga wrote:
On 2013-01-07 09:32:30 +, Walter Bright said:
http://fgda.pl/post/8/a-look-at-the-d-programming-language
Now on Reddit:
http://www.reddit.com/r/programming/comments/1647y1/a_look_at_the_d_programming_language_by_ferdynand/
thedeemon:
I had the impression that Rust was at embryonic stage
Beside reading/seeing some tutorials, blog posts and talks, I
have used Rust only for little experiments, so I don't know a lot
about it.
Compared to D it's less finished, but at version 0.5 most of its
parts/syntax seems
On 2013-01-07 12:55, nazriel wrote:
Anyways, great read. Also nice to see that more and more Polish people are
getting interested in D Programming Language. Maybe in near future I will be
able to meet someone in real world living close to me and drink some beer and
talk about D.
Who knows.
On 2013-01-07 14:31, Chris wrote:
(one more Fibbonacci example and I'll go maD!)
Sorry for using the most overused one. :)
However, in order to convince people to use D for new projects,
it would be nice to have some practical real-world examples
and possibly a list of Made with D-software.
On Monday, 7 January 2013 at 16:57:05 UTC, FG wrote:
Who knows. Maybe there will even be a D conference in Poland in
our lifetime. ;)
Not sure if you were implying this, but actually there was a D
conference in Poland already, the Tango Conference in 2008. ;)
David
On 2013-01-07 18:20, David Nadlinger wrote:
Not sure if you were implying this, but actually there was a D conference in
Poland already, the Tango Conference in 2008. ;)
Oh. I didn't know much about D back then and haven't tried Tango.
IIRC I only started following D after regular expressions
On Monday, 7 January 2013 at 17:20:23 UTC, David Nadlinger wrote:
On Monday, 7 January 2013 at 16:57:05 UTC, FG wrote:
Who knows. Maybe there will even be a D conference in Poland
in our lifetime. ;)
Not sure if you were implying this, but actually there was a D
conference in Poland already,
On 1/7/2013 5:31 AM, Chris wrote:
Nice article. Once I have enough time I would like to write a short article
about how D has solved practical issues for me.
Please do!
I think it is not enough to talk
about all the features of the language (templates, GC) without giving practical
examples
Cool article.
Most of my favorite features are just skipped but hey, you can't
cover everything in an overview! Plus, every new article
describing D's is important.
What's he saying about delete being deprecated? Is that true?
Are we talking about that delete:
class {
new( size_t size )
On Monday, 7 January 2013 at 21:49:12 UTC, Phil Lavoie wrote:
Cool article.
Most of my favorite features are just skipped but hey, you
can't cover everything in an overview! Plus, every new article
describing D's is important.
What's he saying about delete being deprecated? Is that true?
On Monday, 7 January 2013 at 21:49:12 UTC, Phil Lavoie wrote:
Or the global one he uses?
Both actually, iirc. delete foo; is discouraged in favor of a
library function destroy(foo) (or something, the name has changed
once), and the class allocators can be done at the creation site
On Monday, 7 January 2013 at 19:59:44 UTC, Walter Bright wrote:
On 1/7/2013 5:31 AM, Chris wrote:
Nice article. Once I have enough time I would like to write a
short article
about how D has solved practical issues for me.
Please do!
I'd love to.
I think it is not enough to talk
about
44 matches
Mail list logo
