"QUS" <qus@go2.pl> wrote in message news:bha5i4$9g6$1@digitaldaemon.com...
> Can you also explain me what exactly are the outstanding bugs:
> a.. Array op= operations are not implemented.
> a.. Property gettor/settor not implemented.

Not sure what you mean. Those two features are described in the spec, but are not implemented.

Correct, \n is a string literal now, not a character literal. The replacement is:

char c = '\n';

"Russ Lewis" <spamhole-2001-07-16@deming-os.org> wrote in message news:bhb92r$1ehk$1@digitaldaemon.com...
> This code no longer works:
> char c = \n;
>
> Walter wrote:
> > Many bugs fixed. Several requested syntax changes, some will break
existing
> > code, but the fixes are quick & easy.
> >
> > http://www.digitalmars.com/d/changelog.html
>

that does not make sence to me!
why '\n' char \n string.  "\n" is single char string anyway or have that
change ??
so were back to '\\' instead or '\'
the old system make more sence (to me) [now I'd got used to it]
char c = \\; char c ='\';
char[] s = "\\";  char[]s = what-ever-ppl-ended-up-using-for-wytiwyg-strings
char c = \n ;
char[] s ="\n";
there is no need to every have escapes in char literals with '   ' they are
only one char! or are you supporting the gcc charstring to int
int i = 'abcd'; (used  for example in palmos dev for the 32 bit id's as 4
ascii chars)

what was chosen for the what-you-type-is-what-you-get
the D equiv of the perl
$foo = <<'END'
.....
END

as its not in the docs.

"Walter" <walter@digitalmars.com> wrote in message news:bhbctl$1idr$2@digitaldaemon.com...
>
> Correct, \n is a string literal now, not a character literal. The replacement is:
>
> char c = '\n';
>
> "Russ Lewis" <spamhole-2001-07-16@deming-os.org> wrote in message news:bhb92r$1ehk$1@digitaldaemon.com...
> > This code no longer works:
> > char c = \n;
> >
> > Walter wrote:
> > > Many bugs fixed. Several requested syntax changes, some will break
> existing
> > > code, but the fixes are quick & easy.
> > >
> > > http://www.digitalmars.com/d/changelog.html
> >
>
>

What changed was the implicit cast of a single character string to a character literal. The trouble was, there were many cases where the conversions were ambiguous, and I don't like inventing arbitrary rules to disambiguate them. Better to have it unambiguous from the start.

"Mike Wynn" <mike.wynn@l8night.co.uk> wrote in message news:bhbea4$1juh$1@digitaldaemon.com...
> that does not make sence to me!
> why '\n' char \n string.  "\n" is single char string anyway or have that
> change ??
> so were back to '\\' instead or '\'
> the old system make more sence (to me) [now I'd got used to it]
> char c = \\; char c ='\';
> char[] s = "\\";  char[]s =
what-ever-ppl-ended-up-using-for-wytiwyg-strings
> char c = \n ;
> char[] s ="\n";
> there is no need to every have escapes in char literals with '   ' they
are
> only one char! or are you supporting the gcc charstring to int
> int i = 'abcd'; (used  for example in palmos dev for the 32 bit id's as 4
> ascii chars)
>
> what was chosen for the what-you-type-is-what-you-get
> the D equiv of the perl
> $foo = <<'END'
> .....
> END
>
> as its not in the docs.
>
> "Walter" <walter@digitalmars.com> wrote in message news:bhbctl$1idr$2@digitaldaemon.com...
> >
> > Correct, \n is a string literal now, not a character literal. The replacement is:
> >
> > char c = '\n';
> >
> > "Russ Lewis" <spamhole-2001-07-16@deming-os.org> wrote in message news:bhb92r$1ehk$1@digitaldaemon.com...
> > > This code no longer works:
> > > char c = \n;
> > >
> > > Walter wrote:
> > > > Many bugs fixed. Several requested syntax changes, some will break
> > existing
> > > > code, but the fixes are quick & easy.
> > > >
> > > > http://www.digitalmars.com/d/changelog.html
> > >
> >
> >
>
>

On Tue, 12 Aug 2003 11:48:24 -0700 (08/13/03 04:48:24)
, Walter <walter@digitalmars.com> wrote:

>
> "QUS" <qus@go2.pl> wrote in message news:bha5i4$9g6$1@digitaldaemon.com...
>> Can you also explain me what exactly are the outstanding bugs:
>> a.. Array op= operations are not implemented.
>> a.. Property gettor/settor not implemented.
>
> Not sure what you mean. Those two features are described in the spec, but
> are not implemented.
>

I suspect that "QUS" was being a bit too subtle. I read it that he was suggesting that you are implementing 'trivial' or non-urgent enhancements at the expense of implementing stuff which is already documented.

Just a matter of priorities, I guess.

-- 
Derek

"Derek Parnell" <derek.parnell@no.spam> wrote in message news:oprttilipb59ej19@news.digitalmars.com...
> On Tue, 12 Aug 2003 11:48:24 -0700 (08/13/03 04:48:24)
> , Walter <walter@digitalmars.com> wrote:
> > "QUS" <qus@go2.pl> wrote in message news:bha5i4$9g6$1@digitaldaemon.com...
> >> Can you also explain me what exactly are the outstanding bugs:
> >> a.. Array op= operations are not implemented.
> >> a.. Property gettor/settor not implemented.
> > Not sure what you mean. Those two features are described in the spec,
but
> > are not implemented.
> I suspect that "QUS" was being a bit too subtle. I read it that he was
> suggesting that you are implementing 'trivial' or non-urgent enhancements
> at the expense of implementing stuff which is already documented.
> Just a matter of priorities, I guess.

I tend to prefer getting all the nits out of the way before implementing major things. It makes it easier to focus.

Bug:

void main() { char x='á'; }

invalid UTF-8 sequence

I must admit I don't know about encoding and such, but that just doesn't
make sense to me.
(I think it doesn't work for anything not 7 bit ascii, but I don't know. It
doesn't work with dchar either)

————————————————————————— Carlos Santander


---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.509 / Virus Database: 306 - Release Date: 2003-08-12

"Derek Parnell" <derek.parnell@no.spam> wrote in message news:oprttilipb59ej19@news.digitalmars.com...
> On Tue, 12 Aug 2003 11:48:24 -0700 (08/13/03 04:48:24)
> , Walter <walter@digitalmars.com> wrote:
>
> >
> > "QUS" <qus@go2.pl> wrote in message news:bha5i4$9g6$1@digitaldaemon.com...
> >> Can you also explain me what exactly are the outstanding bugs:
> >> a.. Array op= operations are not implemented.
> >> a.. Property gettor/settor not implemented.
> >
> > Not sure what you mean. Those two features are described in the spec,
but
> > are not implemented.
> >
>
> I suspect that "QUS" was being a bit too subtle. I read it that he was suggesting that you are implementing 'trivial' or non-urgent enhancements at the expense of implementing stuff which is already documented.
>
> Just a matter of priorities, I guess.
>
Naaaah... I just wanted to know what these features do :-)

On Wed, 13 Aug 2003 08:30:05 +0200 (08/13/03 16:30:05)
, QUS <qus@go2.pl> wrote:

>
> "Derek Parnell" <derek.parnell@no.spam> wrote in message
> news:oprttilipb59ej19@news.digitalmars.com...
>> On Tue, 12 Aug 2003 11:48:24 -0700 (08/13/03 04:48:24)
>> , Walter <walter@digitalmars.com> wrote:
>>
>> >
>> > "QUS" <qus@go2.pl> wrote in message
>> > news:bha5i4$9g6$1@digitaldaemon.com...
>> >> Can you also explain me what exactly are the outstanding bugs:
>> >> a.. Array op= operations are not implemented.
>> >> a.. Property gettor/settor not implemented.
>> >
>> > Not sure what you mean. Those two features are described in the spec,
> but
>> > are not implemented.
>> >
>>
>> I suspect that "QUS" was being a bit too subtle. I read it that he was
>> suggesting that you are implementing 'trivial' or non-urgent enhancements
>> at the expense of implementing stuff which is already documented.
>>
>> Just a matter of priorities, I guess.
>>
> Naaaah... I just wanted to know what these features do :-)
>

Ooops, Sorry.



-- 
Derek

"QUS" <qus@go2.pl> wrote in message news:bhclj2$2ncv$1@digitaldaemon.com...
> > >> Can you also explain me what exactly are the outstanding bugs:
> > >> a.. Array op= operations are not implemented.
> > >> a.. Property gettor/settor not implemented.
> Naaaah... I just wanted to know what these features do :-)

Array op= are ways to work on all the elements of an array in parallel, like for example OR'ing two bit vectors together. The gettor/settor is a way to access member functions as if they were member variables.