On Mon, Feb 6, 2012 at 9:35 PM, Sergei Gorelkin sergei_gorel...@mail.ru wrote:
So, this is basically a first step of locking Windows RTL to use utf-8 by
default
No, it will not use UTF-8 by default because that would break
compatibility. It will use the system encoding by default and you can
On Tue, 7 Feb 2012, Felipe Monteiro de Carvalho wrote:
On Mon, Feb 6, 2012 at 9:35 PM, Sergei Gorelkin sergei_gorel...@mail.ru wrote:
So, this is basically a first step of locking Windows RTL to use utf-8 by
default
No, it will not use UTF-8 by default because that would break
Felipe Monteiro de Carvalho schrieb:
Hello,
SysUtils for Windows utilizes only A Windows APIs, while it could use
W APIs in Windows NT. The attached patch starts correcting improving
the situation.
Advantages of the patch:
* Allows for unicode file names in TStringList.LoadFromFile if you
Michael Van Canneyt schrieb:
As you know, we are very keen on backwards compatibility.
ACK.
Are you sure that if a AnsiString filename which contains
codepage-specific characters is used to open a file, it will still open
the same file after this patch is applied ?
Win32 filesystems
steve smithers schrieb:
Base / Displacement consists of a 16 bit value, the first 4 bits enumerate a
register, and the other 12 bits hold a displacement from 0 to 4095. The actual
or Effective address for each storage operand is calculated as the unsigned
addition of the value held in the base
In our previous episode, Felipe Monteiro de Carvalho said:
No, it will not use UTF-8 by default because that would break
compatibility. It will use the system encoding by default and you can
use SetMultiByteConversionCodePage to change it to use UTF-8.
Note that this might sound useful now
In our previous episode, Hans-Peter Diettrich said:
IMO a more radical solution is desireable, WRT Win9x. Did anybody test
already, how FPC/Lazarus apps behave on such a system, which does not
support themes etc., and does not even support Unicode without system
updates?
I'd split the
steve smithers wrote:
Episode 3. Addressing and it's limits Part One!
Steve, are you OK if I archive this into the Wiki so it's easily
accessible in the future?
Does the list owner (Jonas?) have any complaints about this on account
of copyright etc.?
--
Mark Morgan Lloyd
markMLl .AT.
Hans-Peter Diettrich wrote:
steve smithers schrieb:
Base / Displacement consists of a 16 bit value, the first 4 bits
enumerate a
register, and the other 12 bits hold a displacement from 0 to 4095.
The actual
or Effective address for each storage operand is calculated as the
unsigned
addition
On 07 Feb 2012, at 12:29, Mark Morgan Lloyd wrote:
steve smithers wrote:
Episode 3. Addressing and it's limits Part One!
Steve, are you OK if I archive this into the Wiki so it's easily
accessible in the future?
Does the list owner (Jonas?) have any complaints about this on
account
On 07.02.2012 18:01, Felipe Monteiro de Carvalho wrote:
Stay tunned for the next chapters of the Unicode wars =)
Here we agree... ;) *fetches popcorn*
Regards,
Sven
___
fpc-devel maillist - fpc-devel@lists.freepascal.org
Hans-Peter Diettrich drdiettri...@aol.com wrote on Tue, 07 Feb 2012
09:12:53 +0100
Base / Displacement consists of a 16 bit value, the first 4 bits enumerate a
register, and the other 12 bits hold a displacement from 0 to 4095. The
actual
or Effective address for each storage
Mark Morgan Lloyd wrote Tue, 07 Feb 2012 11:29:01 +
Steve, are you OK if I archive this into the Wiki so it's easily
accessible in the future?
I have no issue with that at all.
Does the list owner (Jonas?) have any complaints about this on account
of copyright etc.?
If there any
steve smithers wrote:
Mark Morgan Lloyd wrote Tue, 07 Feb 2012 11:29:01 +
Steve, are you OK if I archive this into the Wiki so it's easily
accessible in the future?
I have no issue with that at all.
Does the list owner (Jonas?) have any complaints about this on account
of copyright
steve smithers wrote:
These systems have had had 32 bit compilers since the mid 1960's, it's not
rocket science, just computer science. A version of C was implemented on 360
machines at Bell Labs long before it became a portable system. The architecture
produces problems, but these are
Episode 4. Addressing and it's limits Part Two
So we have seen that Base / Displacement will handle addresses up to a
reasonable size. This should cover most of the requirements. But there are
still issues that have to be resolved, we need the ability to address more. The
way we do this is
16 matches
Mail list logo
