D - DMD 0.69 release
- "Walter" <walter digitalmars.com> Aug 11 2003
- Ant <Ant_member pathlink.com> Aug 11 2003
- Ant <Ant_member pathlink.com> Aug 11 2003
- "Walter" <walter digitalmars.com> Aug 11 2003
- "j anderson" <anderson badmama.com.au.REMOVE> Aug 11 2003
- "Walter" <walter digitalmars.com> Aug 11 2003
- "QUS" <qus go2.pl> Aug 12 2003
- "Walter" <walter digitalmars.com> Aug 12 2003
- Derek Parnell <derek.parnell no.spam> Aug 12 2003
- "Walter" <walter digitalmars.com> Aug 12 2003
- "QUS" <qus go2.pl> Aug 12 2003
- Derek Parnell <derek.parnell no.spam> Aug 12 2003
- "Walter" <walter digitalmars.com> Aug 13 2003
- John Reimer <jjreimer telus.net> Aug 12 2003
- "Sean L. Palmer" <palmer.sean verizon.net> Aug 12 2003
- Russ Lewis <spamhole-2001-07-16 deming-os.org> Aug 12 2003
- "Walter" <walter digitalmars.com> Aug 12 2003
- "Mike Wynn" <mike.wynn l8night.co.uk> Aug 12 2003
- "Walter" <walter digitalmars.com> Aug 12 2003
- "Carlos Santander B." <carlos8294 msn.com> Aug 12 2003
- "Walter" <walter digitalmars.com> Aug 13 2003
- "Carlos Santander B." <carlos8294 msn.com> Aug 13 2003
- "Walter" <walter digitalmars.com> Aug 13 2003
- "Walter" <walter digitalmars.com> Aug 13 2003
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
Aug 11 2003
Great! Just compiled DUI with 0.69; I realy like the -op option (didn't test yet) you forgot to update the Linux -o options (or maybe not - just didn't have to time) Ant In article <bh9pj6$2t30$1 digitaldaemon.com>, Walter says...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
Aug 11 2003
(where is my Re:Re:? here it goes again...)you forgot to update the Linux -o options
I mean on the web page. Ant
Aug 11 2003
"Walter" <walter digitalmars.com> Fixed. Thanks, -Walter "Ant" <Ant_member pathlink.com> wrote in message news:bh9tfm$319g$1 digitaldaemon.com...(where is my Re:Re:? here it goes again...)you forgot to update the Linux -o options
I mean on the web page. Ant
Aug 11 2003
wysiwyg strings are not r"string", not 'string'.? Did you mean... r"string" and 'string' are both not wysiwyg strings. J Anderson. "Walter" <walter digitalmars.com> wrote in message news:bh9pj6$2t30$1 digitaldaemon.com...Many bugs fixed. Several requested syntax changes, some will break
code, but the fixes are quick & easy. http://www.digitalmars.com/d/changelog.html
Aug 11 2003
r"string" is a wysiwyg string 'string' is a character literal "j anderson" <anderson badmama.com.au.REMOVE> wrote in message news:bh9voo$29e$1 digitaldaemon.com...wysiwyg strings are not r"string", not 'string'.? Did you mean... r"string" and 'string' are both not wysiwyg strings. J Anderson. "Walter" <walter digitalmars.com> wrote in message news:bh9pj6$2t30$1 digitaldaemon.com...Many bugs fixed. Several requested syntax changes, some will break
code, but the fixes are quick & easy. http://www.digitalmars.com/d/changelog.html
Aug 11 2003
http://www.digitalmars.com/d/changelog.html
Cite (from the page) * wysiwyg strings are not r"string", not 'string'. * A bit confusing :-) But I guess it should be: * wysiwyg strings are noW r"string", not 'string'. * * 0b... numeric literals now work under Linux. * Geee! The 0b was even mentioned in the PDF manual, and I came here and requested it. I feel so stupid now :-) * Integer and floating point literals can now have embedded _ for formatting purposes. * Wow! So many quick fixes and addition. I am really happy to see all this! :-) Can you also explain me what exactly are the outstanding bugs: a.. Array op= operations are not implemented. a.. Property gettor/settor not implemented. Cheers, QUS
Aug 12 2003
"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.
Aug 12 2003
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
Aug 12 2003
"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.
are not implemented.
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.
Aug 12 2003
"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,
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.
Aug 12 2003
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,
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.
Ooops, Sorry. -- Derek
Aug 12 2003
"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.
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.
Aug 13 2003
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
Wow! A bit of a compromise with wysiwyg strings: `string` (backquotes) are also wysiwyg strings. Thanks! Later, John
Aug 12 2003
You are the man! Lots of goodies in this one. ;) Sean "Walter" <walter digitalmars.com> wrote in message news:bh9pj6$2t30$1 digitaldaemon.com...Many bugs fixed. Several requested syntax changes, some will break
code, but the fixes are quick & easy. http://www.digitalmars.com/d/changelog.html
Aug 12 2003
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
Aug 12 2003
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
code, but the fixes are quick & easy. http://www.digitalmars.com/d/changelog.html
Aug 12 2003
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
code, but the fixes are quick & easy. http://www.digitalmars.com/d/changelog.html
Aug 12 2003
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 =
char c = \n ; char[] s ="\n"; there is no need to every have escapes in char literals with ' ' they
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
code, but the fixes are quick & easy. http://www.digitalmars.com/d/changelog.html
Aug 12 2003
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
Aug 12 2003
"Carlos Santander B." <carlos8294 msn.com> wrote in message news:bhccj1$2emj$1 digitaldaemon.com...Bug: void main() { char x='á'; } invalid UTF-8 sequence
It is an invalid utf-8 sequence. Code pages with values 0x80-0xFF won't work with UTF-8.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.
doesn't work with dchar either)
The source text needs to be UTF-8, UTF-16 or UCS-4. Does your text editor have a setting for that? (Notepad does.) What I apparently need to write is a translator from the usual code pages to UTF-8. Anyone have a guide to the mappings?
Aug 13 2003
"Walter" <walter digitalmars.com> wrote in message news:bhe1u2$12n1$1 digitaldaemon.com... | | It is an invalid utf-8 sequence. Code pages with values 0x80-0xFF won't work | with UTF-8. So, what should I use instead? | | The source text needs to be UTF-8, UTF-16 or UCS-4. Does your text editor | have a setting for that? (Notepad does.) | I use SciTE, and if I save in UTF-8 encoding, I get: test.d(1): unsupported char 0xef test.d(1): unsupported char 0xbb test.d(1): unsupported char 0xbf ————————————————————————— 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
Aug 13 2003
"Carlos Santander B." <carlos8294 msn.com> wrote in message news:bhe3r9$14jq$1 digitaldaemon.com..."Walter" <walter digitalmars.com> wrote in message news:bhe1u2$12n1$1 digitaldaemon.com... | | It is an invalid utf-8 sequence. Code pages with values 0x80-0xFF won't work | with UTF-8. So, what should I use instead? | | The source text needs to be UTF-8, UTF-16 or UCS-4. Does your text
| have a setting for that? (Notepad does.) | I use SciTE, and if I save in UTF-8 encoding, I get: test.d(1): unsupported char 0xef test.d(1): unsupported char 0xbb test.d(1): unsupported char 0xbf
Email me the source file, and I'll have a look.
Aug 13 2003
I found & fixed the problem. In the meantime, you can work around it by either lopping the first 3 bytes off of the file or try writing it out as UTF-16 instead.
Aug 13 2003