On 27/09/17 09:16, Graeme Geldenhuys via Lazarus wrote:
> On 2017-09-27 03:51, Marcos Douglas B. Santos via Lazarus wrote:
>> A constant that can change...
>
>
> Yeah, that concept still blows my mind. [figuratively speaking] They
> should shoot the developer that came up with that idea - and the
On Wed, Sep 27, 2017 at 7:05 AM, Juha Manninen via Lazarus
wrote:
> On Tue, Sep 26, 2017 at 10:52 PM, Marcos Douglas B. Santos via Lazarus
> [...]
> About the string constant concatenation, just use variables when it is proper:
> const
> V1: string = 'a';
> var
> S1: String;
> ... later in cod
On Wed, Sep 27, 2017 at 5:16 AM, Graeme Geldenhuys via Lazarus
wrote:
> On 2017-09-27 03:51, Marcos Douglas B. Santos via Lazarus wrote:
>>
>> A constant that
>> can change...
>
>
>
> Yeah, that concept still blows my mind. [figuratively speaking] They should
> shoot the developer that came up wit
On Tue, Sep 26, 2017 at 10:52 PM, Marcos Douglas B. Santos via Lazarus
wrote:
> So we can say that Lazarus code do not use XPath to work with XML, right?
No I cannot say much about the issue. I didn't try it myself.
I understood Mattias and Michael V.C. have plans to migrate the XML
units to FCL
On 2017-09-27 03:51, Marcos Douglas B. Santos via Lazarus wrote:
A constant that
can change...
Yeah, that concept still blows my mind. [figuratively speaking] They
should shoot the developer that came up with that idea - and the team
leader that approved it.
Regards,
Graeme
--
_
On Tue, Sep 26, 2017 at 5:06 PM, Howard Page-Clark via Lazarus
wrote:
> On 26/09/17 20:51, Marcos Douglas B. Santos via Lazarus wrote:
>>
>> I understood that I can use like this:
>> const
>>VALUE: string = 'áéíóú';
>>
>> Not like this:
>> const
>>VALUE = 'áéíóú';
>>
>> Right?
>> But this
On 26/09/17 20:51, Marcos Douglas B. Santos via Lazarus wrote:
I understood that I can use like this:
const
VALUE: string = 'áéíóú';
Not like this:
const
VALUE = 'áéíóú';
Right?
But this is not compile:
const
V1: string = 'a';
V2: string = V1 + 'b';
You can't do that in a const dec
On Tue, Sep 26, 2017 at 9:09 AM, Juha Manninen via Lazarus
wrote:
> On Tue, Sep 26, 2017 at 12:11 AM, Marcos Douglas B. Santos via Lazarus
> wrote:
>> Yeah, but DOM uses DOMString, which is WideString.
>> Lazarus uses UTF8 and have a laz2_DOM that uses "string", which is
>> UTF8, but I cannot use
On Tue, Sep 26, 2017 at 6:31 AM, Juha Manninen via Lazarus
wrote:
> On Tue, Sep 26, 2017 at 4:37 AM, Marcos Douglas B. Santos via Lazarus
> wrote:
>> But according with this table, I shouldn't do that because so many
>> problems could happen.
>> http://wiki.freepascal.org/Unicode_Support_in_Lazar
On 26.09.2017 11:31, Juha Manninen via Lazarus wrote:
Maybe there still is a valid reason to use codepages but I don't know
what it is.
POS receipt printers :)
zeljko
--
___
Lazarus mailing list
Lazarus@lists.lazarus-ide.org
https://lists.lazarus-id
On Tue, Sep 26, 2017 at 12:11 AM, Marcos Douglas B. Santos via Lazarus
wrote:
> Yeah, but DOM uses DOMString, which is WideString.
> Lazarus uses UTF8 and have a laz2_DOM that uses "string", which is
> UTF8, but I cannot use this unit with XPath unit, which needs a
> TXMLDocument that works with W
On Tue, Sep 26, 2017 at 4:37 AM, Marcos Douglas B. Santos via Lazarus
wrote:
> But according with this table, I shouldn't do that because so many
> problems could happen.
> http://wiki.freepascal.org/Unicode_Support_in_Lazarus#Without_.7B.24codepage_utf8.7D_or_compilerswitch_-FcUTF8
No. It works
I do not see how it is a hack, when you have a function taking a null
terminated string of a specific character type (in this case PWideChar) and
you only have the generic string type you don't know what format the
underlying memory of the string is so you cannot pass it as a pointer to
the functio
On Mon, Sep 25, 2017 at 9:52 PM, Juha Manninen via Lazarus
wrote:
> On Tue, Sep 26, 2017 at 3:14 AM, Marcos Douglas B. Santos via Lazarus
> wrote:
>> So, you mean that I cannot declare a constant without specify the
>> type. The language allow me but it won't work?
>
> Yes you can declare a strin
On Tue, Sep 26, 2017 at 3:14 AM, Marcos Douglas B. Santos via Lazarus
wrote:
> So, you mean that I cannot declare a constant without specify the
> type. The language allow me but it won't work?
Yes you can declare a string constant without specifying the type.
> 3.1. "When a parameter type is a
On Mon, Sep 25, 2017 at 7:52 PM, Juha Manninen via Lazarus
wrote:
> Marcos Douglas, this wiki page answers all your questions about using
> Unicode with Lazarus:
> http://wiki.freepascal.org/Unicode_Support_in_Lazarus
OK, let's talk:
1. "Using UTF-8 in non-LCL programs"
"In a non-LCL project ad
And more ...
Marcos Douglas, the Unicode solution in Lazarus works amazingly well
when your data is Unicode from the start.
It only has trouble with Windows system codepages but they can be
converted, too.
Question: what is the fundamental problem? Why can't you use the
system as it is advertised
Marcos Douglas, this wiki page answers all your questions about using
Unicode with Lazarus:
http://wiki.freepascal.org/Unicode_Support_in_Lazarus
On Mon, Sep 25, 2017 at 9:19 PM, Ondrej Pokorny via Lazarus
wrote:
> You will have to write your own methods with IFDEF-ed code for things
> where it
On Mon, Sep 25, 2017 at 6:23 PM, Sven Barth via Lazarus
wrote:
> On 25.09.2017 23:11, Marcos Douglas B. Santos via Lazarus wrote:
[...]
>>> The flags are -MDelphiUnicode, -MDelphi or -MObjFPC.
>>> But they only compile the units with sources in the unit path, which
>>> excludes all FPC units.
On Mon, Sep 25, 2017 at 6:10 PM, Sven Barth via Lazarus
wrote:
> On 25.09.2017 22:18, Marcos Douglas B. Santos via Lazarus wrote:
>> [...]
>> Yes, but using {$modeswitch unicodestrings}, at least in a certain
>> unit, should work with the same code between compilers because
>> "string", for that u
On 25.09.2017 23:11, Marcos Douglas B. Santos via Lazarus wrote:
>>> [...]
>>> I know almost nothing about compilers. But IMHO, the compiler should
>>> have which it already have: "string", which is an alias.
>>> Then, for each OS, we should pass one argument like (simplifying):
>>> -S=UnicodeStrin
Hi Mattias,
On Mon, Sep 25, 2017 at 5:45 PM, Mattias Gaertner via Lazarus
wrote:
> On Mon, 25 Sep 2017 17:18:05 -0300
> "Marcos Douglas B. Santos via Lazarus"
> wrote:
>
>>[...]
>
> Your first email does not contain a simple Lazarus+string example. I
> see an example for LCL+unicodestring.
Yes,
On 25.09.2017 22:18, Marcos Douglas B. Santos via Lazarus wrote:
> Hi Sven,
> First of all, thanks for your time to answer me.
>
> On Mon, Sep 25, 2017 at 4:43 PM, Sven Barth via Lazarus
> wrote:
>> On 25.09.2017 20:51, Marcos Douglas B. Santos via Lazarus wrote:
>>> I understand use IFDEF to com
On Mon, 25 Sep 2017 17:18:05 -0300
"Marcos Douglas B. Santos via Lazarus"
wrote:
>[...]
> Yes, but using {$modeswitch unicodestrings}, at least in a certain
> unit, should work with the same code between compilers because
> "string", for that unit, is UnicodeString as Delphi string is, no?
The i
Hi Sven,
First of all, thanks for your time to answer me.
On Mon, Sep 25, 2017 at 4:43 PM, Sven Barth via Lazarus
wrote:
> On 25.09.2017 20:51, Marcos Douglas B. Santos via Lazarus wrote:
>> I understand use IFDEF to compile in different platforms like Windows
>> vs... err... Haiku. Of Linux vs N
On 25.09.2017 20:51, Marcos Douglas B. Santos via Lazarus wrote:
> I understand use IFDEF to compile in different platforms like Windows
> vs... err... Haiku. Of Linux vs Nintendo Wii...
> But why should I use IFDEF in a code that should be the same in both
> compilers (FPC vs Delphi)?
Because the
I understand use IFDEF to compile in different platforms like Windows
vs... err... Haiku. Of Linux vs Nintendo Wii...
But why should I use IFDEF in a code that should be the same in both
compilers (FPC vs Delphi)?
Is it because the string type is not Unicode? OK, so I want to convert
all to use UTF
On Mon, Sep 25, 2017 at 3:19 PM, Ondrej Pokorny via Lazarus
wrote:
> On 25.09.2017 20:02, Marcos Douglas B. Santos via Lazarus wrote:
>>
>> May I code using just "string"?
>
>
> Yes. LCL is ANSI/UTF8 only, so is TStrings.
>
> You can write Lazarus+Delphi compatible code without a lot of problems.
On 25.09.2017 20:02, Marcos Douglas B. Santos via Lazarus wrote:
May I code using just "string"?
Yes. LCL is ANSI/UTF8 only, so is TStrings.
You can write Lazarus+Delphi compatible code without a lot of problems.
Just use the string type. The only thing you have to be aware is that in
Delphi
Hi,
Yes, yes... another email about Unicode, because it has not been
completed yet. Sorry.
I would like to know how I can develop CLI and GUI (Lazarus) programs
using just UnicodeString, making them all compatible with Delphi
compiler.
My environment is:
Lazarus 1.9.0 r54784 FPC 3.0.1 i386-win32-
30 matches
Mail list logo