So I think the next *big* step from here, in D3 or some other
D-derived
language, would be easing the creation of ranges. For example, a
special low-boilerplate syntax for creating bidirectional and
random-access ranges. Or for input (or maybe even forward)
ranges, a
C#-style compile-time
On Wednesday, 3 October 2012 at 06:15:32 UTC, jerro wrote:
So I think the next *big* step from here, in D3 or some other
D-derived
language, would be easing the creation of ranges. For example,
a
special low-boilerplate syntax for creating bidirectional and
random-access ranges. Or for input
Hi,
I incorrectly mentioned example I tried, that wass http_server.
Now it compiled, but immediately stopped, and the message box with this
error appeared:
The application was unable to start correctly (0xc022). Click OK to
close the application.
Maybe this is a problem on my system, but
ixid:
The article contains a bug due to the pernicious behaviour of
seedless reduce.
Hopefully Walter will be able to fix the article.
Bye,
bearophile
The 0x022 error means that the operating system fired a
STATUS_ACCESS_DENIED exception at application startup (while loading dll
dependencies etc.) for some reason. No idea why that happens (works for
me), but I would check if there might be some kind of special security
policies on the
Currently, toUpper() (and probably toLower()) does not handle
greek characters correctly. I fixed toUpper() by making a another
function for greek characters
// called if (c = 0x387 c = 0x3CE)
dchar toUpperGreek(dchar c)
{
if( c = 'α' c = 'ω' )
{
if( c == 'ς'
On Wednesday, 3 October 2012 at 10:56:11 UTC, Minas wrote:
Currently, toUpper() (and probably toLower()) does not handle
greek characters correctly. I fixed toUpper() by making a
another function for greek characters
// called if (c = 0x387 c = 0x3CE)
dchar toUpperGreek(dchar c)
{
Andrei Alexandrescu wrote:
http://www.reddit.com/r/programming/comments/10u6sk/component_programming_in_d/
Nice article!
There, I found an interesting way of writing ranges that are not
explicitly initialized:
private import core.stdc.stdio;
struct StdinByChar {
@property
Piotr Szturmaj wrote:
guess that's necessary because structs doesn't have () ctors.
should be don't
On Wednesday, 3 October 2012 at 10:56:11 UTC, Minas wrote:
Currently, toUpper() (and probably toLower()) does not handle
greek characters correctly. I fixed toUpper() by making a
another function for greek characters
// called if (c = 0x387 c = 0x3CE)
dchar toUpperGreek(dchar c)
{
On Wednesday, 3 October 2012 at 13:27:25 UTC, Paulo Pinto wrote:
On Wednesday, 3 October 2012 at 10:56:11 UTC, Minas wrote:
Currently, toUpper() (and probably toLower()) does not handle
greek characters correctly. I fixed toUpper() by making a
another function for greek characters
// called
I have some mixed feeling about component programming: add in all
the examples the requirement to give the context (line number for
example) where something happened (either a match or an error)
and suddendly component programming becomes much more tricky!!
So for me component programming
On Wednesday, 3 October 2012 at 10:56:11 UTC, Minas wrote:
Do you think it should stay like that or I should copy-paste it
in the body of toUpper()?
I'm going to fix toLower() as well and make a pull request.
In any case, you should coordinate with Dmitry Olshansky, since
he is (was?)
On 03-Oct-12 18:11, Minas wrote:
On Wednesday, 3 October 2012 at 13:27:25 UTC, Paulo Pinto wrote:
On Wednesday, 3 October 2012 at 10:56:11 UTC, Minas wrote:
Currently, toUpper() (and probably toLower()) does not handle greek
characters correctly. I fixed toUpper() by making a another function
On 03-Oct-12 21:10, Ali Çehreli wrote:
On 10/03/2012 03:56 AM, Minas wrote:
Currently, toUpper() (and probably toLower()) does not handle greek
characters correctly. I fixed toUpper() by making a another function for
greek characters
// called if (c = 0x387 c = 0x3CE)
dchar toUpperGreek(dchar
On 03-Oct-12 20:13, David Nadlinger wrote:
On Wednesday, 3 October 2012 at 10:56:11 UTC, Minas wrote:
Do you think it should stay like that or I should copy-paste it in the
body of toUpper()?
I'm going to fix toLower() as well and make a pull request.
In any case, you should coordinate with
On Wednesday, 3 October 2012 at 01:40:05 UTC, ixid wrote:
On Tuesday, 2 October 2012 at 21:27:42 UTC, Andrei Alexandrescu
wrote:
http://www.reddit.com/r/programming/comments/10u6sk/component_programming_in_d/
Andrei
The article contains a bug due to the pernicious behaviour of
seedless
On 10/03/2012 11:21 AM, Dmitry Olshansky wrote:
On 03-Oct-12 21:10, Ali Çehreli wrote:
On 10/03/2012 03:56 AM, Minas wrote:
[...]
map['ά'] = 'Ά';
[...]
Glad you showed up!
Why? Do I whine better? :p
One and by far the most useful case is case-insensitive matching.
That being said this
On 10/03/2012 01:37 PM, Dmitry Olshansky wrote:
On 03-Oct-12 23:56, Ali Çehreli wrote:
If we are talking about the order then this is the way to go:
http://unicode.org/reports/tr10/
Thank you. I wasn't aware of that long read. :)
struct Order
{
int base;
int accent;
int cased;
}
(Of
On 10/03/2012 05:59 PM, renoX wrote:
I have some mixed feeling about component programming: add in all the
examples the requirement to give the context (line number for example)
where something happened (either a match or an error) and suddendly
component programming becomes much more tricky!!
On Wednesday, 26 September 2012 at 18:48:41 UTC, Mike James wrote:
I tried the install detailed on the github page and got the
following error:
C:\D\dmd2\gtkD2\srcdgen
build\gtkD.d(612): Error: module SourceBuffer is in file
'gsv\SourceBuffer.d' wh
ich cannot be read
import path[0] =
21 matches
Mail list logo
