On 11/16/2010 02:52 PM, Paul Breneman wrote:
I try hard to write Pascal programs without using pointers and without
allocating or deallocating memory.
OOpps. How is this possible :) ? But in what way does this help on that
issue ? I do see that memory allocation/deallocation is a source t
On 11/15/2010 02:04 PM, Thaddy wrote: ...
If you want to extend a compiler to allow for garbage collection, would
it not be appropriate to have it manage an additional type of variables
that is supposed to be "garbage collection enabled" pointers and have it
always create double indirect acce
In our previous episode, Hans-Peter Diettrich said:
> >
> > I don't consider it an extreme, on the contrary. Trying to fix this is
> > extreme IMHO.
>
> Sorry, I understood that you want to replace all for loops by iterated
> loops.
Only the ones where surrogates really matter.
> >>> And in
On 11/15/2010 01:24 PM, Marco van de Voort wrote:
Typically I'd iterate by means outside the language (I've used simple iterators
based on a record with a few inline methods in the past), and review the
places where you iterate by char through strings, and reduce it
signficantly.
Since the latt
On 11/17/2010 10:12 AM, Marco van de Voort wrote:
Only the ones where surrogates really matter.
Is is really viable to have the compiler/RTL try to automatically handle
these ugly beasts, rather than presenting them to the poor user as two
separate Unicode characters (and only handle the UTC/U
In our previous episode, Michael Schnell said:
> >
> > Only the ones where surrogates really matter.
> Is is really viable to have the compiler/RTL try to automatically handle
> these ugly beasts,
It is not viable not to. Either you implement unicode or not.
It's an users own choice to not be
On 11/17/2010 12:02 PM, Marco van de Voort wrote:
In our previous episode, Michael Schnell said:
Only the ones where surrogates really matter.
Is is really viable to have the compiler/RTL try to automatically handle
these ugly beasts,
It is not viable not to. Either you implement unicode or no
On 17 Nov 2010, at 12:23, Michael Schnell wrote:
Regarding that handling surrogate pairs needs tables while UTF/UCS
handling can be done by simple algorithms and that (AFAIK) surrogate
pairs are used only in certain environments (Mac and what else ?)
Surrogate pairs have nothing to do with
In our previous episode, Michael Schnell said:
> > It is not viable not to. Either you implement unicode or not.
> >
> > It's an users own choice to not be unicode compliant in his apps (e.g. if he
> > knows he never goes to the Eastern Asiatic market etc), but a runtime should
> > be as unicode co
On 11/17/2010 01:20 PM, Jonas Maebe wrote:
Surrogate pairs have nothing to do with Mac OS X. Surrogate pairs are
required when encoding any codepoint in UTF-16 whose UTF32 value is >=
$1.
In fact I was not aware of the UTF-16 coding scheme. I _supposed_ it
would work similar as UTF-8 (hi
Martin Schreiber wrote:
On Tuesday, 16. November 2010 14.52:12 Paul Breneman wrote:
I'd like to take the minimal distros and add a simple option to use
MSEide and it supports debugging from what I understand. Then maybe
extending that with remote debugging would be the next item.
MSEide is rea
On 11/17/2010 01:32 PM, Marco van de Voort wrote:
Regarding OS X, iirc I saw a mention somewhere that some components of Mac
OS X prefer decomposed characters. (aka UTF-8Mac).
In another forum I saw this mentioned as surrogate pairs. Sorry for the
confusion :(.
-Michael
___
On 11/17/2010 02:10 PM, Paul Breneman wrote:
Martin Schreiber wrote:
On Tuesday, 16. November 2010 14.52:12 Paul Breneman wrote:
I'd like to take the minimal distros and add a simple option to use
MSEide and it supports debugging from what I understand. Then maybe
extending that with remote de
On 17 Nov 2010, at 13:44, Michael Schnell wrote:
In fact I was not aware of the UTF-16 coding scheme. I _supposed_ it
would work similar as UTF-8 (highest bit set => 32 bit value
composed from the 31 remaining bits of this and the next word and
bit 31 reset) and thus could be decoded algor
Marco van de Voort schrieb:
It's an users own choice to not be unicode compliant in his apps (e.g. if he
knows he never goes to the Eastern Asiatic market etc), but a runtime should
be as unicode compliant as reasonably possible.
IMO there exist levels of compliance.
The bottom level supplies
Michael Schnell wrote:
On 11/16/2010 02:52 PM, Paul Breneman wrote:
I try hard to write Pascal programs without using pointers and without
allocating or deallocating memory.
OOpps. How is this possible :) ? But in what way does this help on that
issue ? I do see that memory allocation/de
On 17-11-2010 10:01, Michael Schnell wrote:
On 11/15/2010 02:04 PM, Thaddy wrote: ...
If you want to extend a compiler to allow for garbage collection,
would it not be appropriate to have it manage an additional type of
variables that is supposed to be "garbage collection enabled"
pointers a
17 matches
Mail list logo
