They didn't.
Perhaps he means C#.
But here, AFAIK, string support is very different to what Pascal
programmers are accustomed to. Strings are always constant and can't be
modified, They are created once and discarded completely later.
Something like s[3] := 'x'; is not portable to C#.
-M
Op Wed, 12 Nov 2008, schreef Bernd Mueller:
Unicode support in FPC?
Sorry for jumping in. I am not so much interested in Unicode because I mostly
use shortstrings and ansistrings for performance reasons. But may be it is
worth to look how the gcc people have solved these issues.
They d
Unicode support in FPC?
Sorry for jumping in. I am not so much interested in Unicode because I
mostly use shortstrings and ansistrings for performance reasons. But may
be it is worth to look how the gcc people have solved these issues.
Regards, Bernd.
_
On Wed, Nov 12, 2008 at 10:46 AM, Michael Van Canneyt
<[EMAIL PROTECTED]> wrote:
>> BTW: That component is a lifesaver! It makes setup and configuration
>> of database applications a breeze. :-)
>
> I know, that's what I use it for.
> I developed it years ago. It's been in use for almost 10 years n
On Wed, 12 Nov 2008, Graeme Geldenhuys wrote:
> On Wed, Nov 12, 2008 at 10:28 AM, Michael Van Canneyt
> <[EMAIL PROTECTED]> wrote:
> >>
> >> Is there any chance that the TSQLScript.CommentsInSQL and
> >> TSQLScript.UseCommit properties could be backported from 2.3.1 to
> >> 2.2.3?
> >
> > Yes. W
I' not in that team ;) but I think I did provide a workable suggestion
15 minutes ago in this thread. Of course I have no idea at all if it's
possible to implement this with not too much work for the team members :( .
eg:
* One encoding internally (utf8 maybe)?
I vote for allowing the user t
- widestrings had some bugs at the time and were not reference counted
(Martin did a great job over the years to improve that)
Of course this is a serious argument. I feel that any decent string type
(but pchar :) ) needs to be reference counting. In my "suggestion" mail
10 minutes ago in t
On Wed, Nov 12, 2008 at 10:28 AM, Michael Van Canneyt
<[EMAIL PROTECTED]> wrote:
>>
>> Is there any chance that the TSQLScript.CommentsInSQL and
>> TSQLScript.UseCommit properties could be backported from 2.3.1 to
>> 2.2.3?
>
> Yes. We decided to make a 2.2.4, and this will be in it.
Ah, thanks Mi
On Wed, 12 Nov 2008, Graeme Geldenhuys wrote:
> Hi,
>
> Is there any chance that the TSQLScript.CommentsInSQL and
> TSQLScript.UseCommit properties could be backported from 2.3.1 to
> 2.2.3?
Yes. We decided to make a 2.2.4, and this will be in it.
Michael.
Lazarus assumes that an ansistring contains always utf-8. This is not
generally true.
While this might be true, I think it's a consequence of a shortcoming of
FPC, which simply identifies the types ANSIString and UTF8String. IMHO
(in a future version) it should take care of the encoding of str
Hi,
Is there any chance that the TSQLScript.CommentsInSQL and
TSQLScript.UseCommit properties could be backported from 2.3.1 to
2.2.3?
Regards,
- Graeme -
___
fpGUI - a cross-platform Free Pascal GUI toolkit
http://opensoft.homeip.net/fpgui/
__
11 matches
Mail list logo
