Re: strings and ranges

2013-08-15 Thread monarch_dodra
On Thursday, 15 August 2013 at 00:49:00 UTC, Jason den Dulk wrote: Also, does this mean that if I'm creating an output range for char[], will I need to implement a put(dchar) as well as a put(char)? Unfortunately, right now, yes. "put" doesn't know how to convert on the fly to the right type.

Re: strings and ranges

2013-08-15 Thread Jonathan M Davis
On Thursday, August 15, 2013 02:48:58 Jason den Dulk wrote: > Hello. > > When working with my code I noticed that if I use front on a > char[], it yields a dchar. Am I correct in concluding that it > does a UTF-8 to UTF-32 conversion and popFont will skip the whole > character, not just a code uni

Re: strings and ranges

2013-08-14 Thread anonymous
On Thursday, 15 August 2013 at 00:49:00 UTC, Jason den Dulk wrote: When working with my code I noticed that if I use front on a char[], it yields a dchar. Am I correct in concluding that it does a UTF-8 to UTF-32 conversion and popFont will skip the whole character, not just a code unit? yup

strings and ranges

2013-08-14 Thread Jason den Dulk
Hello. When working with my code I noticed that if I use front on a char[], it yields a dchar. Am I correct in concluding that it does a UTF-8 to UTF-32 conversion and popFont will skip the whole character, not just a code unit? Also, does this mean that if I'm creating an output range for