Martin Schreiber wrote:
FPC fixes_3_0 with the program
"
program json;
{$codepage utf8}
{$ifdef FPC}{$mode objfpc}{$h+}{$endif}
{$ifdef mswindows}{$apptype console}{$endif}
uses
{$ifdef FPC}{$ifdef unix}cthreads,cwstring,{$endif}{$endif}
sysutils;
resourcestring
a = 'aäÄ';
begin
end.
"
Martin Schreiber wrote:
On Thursday 24 September 2015 08:42:11 Jonas Maebe wrote:
I have no idea. I only looked at the compiler/cresstr.pas unit and saw
that the codepage of resource strings stored in the object code is set
to the source file code page. I don't even know how the .rst/.rsj files
On Thursday 24 September 2015 09:21:01 Mattias Gaertner wrote:
> On Thu, 24 Sep 2015 09:10:06 +0200
>
> Martin Schreiber wrote:
> >[...]
> > Another question, it looks to me that -Fcutf8 does not work like
> > {$codepage utf8} for string constants.
>
> What do you mean?
>
If I
On Thu, 24 Sep 2015, Graeme Geldenhuys wrote:
Hi,
I'm using the JSONRTTI unit to successfully save an object to a .json
file. But when loading that file back using TJSONDeStreamer I get a
conversion error due to the Date/Time format.
Here is the code to handle the TDateTime fields of my
Hi,
I'm using the JSONRTTI unit to successfully save an object to a .json
file. But when loading that file back using TJSONDeStreamer I get a
conversion error due to the Date/Time format.
Here is the code to handle the TDateTime fields of my object - I store
them as ISO8601 date/time format.
On 2015-09-24 12:00, Graeme Geldenhuys wrote:
> The problem is, the TJSONDeStreamer doesn't have the equivalent Options
> property or DateTimeFormat property that TJSONStreamer has, so how is it
> supposed to know how to handle Date/Time fields? No wonder it gives a
> Conversion Error.
I had a
On Thu, 24 Sep 2015, Martin Schreiber wrote:
On Monday 21 September 2015 11:06:53 Jonas Maebe wrote:
Martin Schreiber wrote on Sun, 20 Sep 2015:
Are there any changes? How resourcestrings are encoded?
Resourcestrings are stored using the same code page as constant
ansistrings in the
On Thu, 24 Sep 2015 09:10:06 +0200
Martin Schreiber wrote:
>[...]
> Another question, it looks to me that -Fcutf8 does not work like {$codepage
> utf8} for string constants.
What do you mean?
Mattias
___
fpc-pascal maillist -
On Thursday 24 September 2015 09:28:28 Jonas Maebe wrote:
>
> There are several more, including lack of support for non-ansi encoded
> file names and most classes that (still) exist only in ansistring form.
> You can of course create replacements for all of that, but then again,
> you could also
On 2015-09-24 06:55, Martin Schreiber wrote:
> Is this intended? How can translation tools know that the Unicode points must
> be interpreted as utf-8 code units in this case?
I would guess you found a bug or the implementation is incomplete - but
then FPC 3.0 is in rc phase as far as I know.
I
On 2015-09-24 09:09, Martin Schreiber wrote:
> It is an advantage to have pure ASCII files for such data.
Escaped text seems optional, but the UTF-8 encoding seem recommended.
Using non-escaped Unicode text is faster to parse and easier to read [by
a human] - and from my understanding of the RFC
On Thursday 24 September 2015 09:52:34 Jonas Maebe wrote:
> Martin Schreiber wrote:
>
> >>> Another question, it looks to me that -Fcutf8 does not work like
> >>> {$codepage utf8} for string constants. Is this intend?
> >>
> >> I think they should have the same effect.
> >
> > Another bug?
>
> If
On Thu, 24 Sep 2015, Martin Schreiber wrote:
On Thursday 24 September 2015 09:28:28 Jonas Maebe wrote:
Should I make a bug report?
There is already a (very old) bug report for that.
I meant a bug report for the unusual json format.
Please do.
Michael.
On 2015-09-24 08:14, Martin Schreiber wrote:
>> > What did you expect to see ?
>> >
> "
> {"version":1,"strings":[
> {"hash":7200948,"name":"json.a","value":"a\u00E4\u00C4"}
> ]}
> "
>
I would have expected the same as the original.
"
{"version":1,"strings":[
Martin Schreiber wrote:
On Thursday 24 September 2015 09:28:28 Jonas Maebe wrote:
There are several more, including lack of support for non-ansi encoded
file names and most classes that (still) exist only in ansistring form.
You can of course create replacements for all of that, but then again,
On Thursday 24 September 2015 08:42:11 Jonas Maebe wrote:
> Martin Schreiber wrote:
> > FPC fixes_3_0 with the program
> > "
> > program json;
> > {$codepage utf8}
> > {$ifdef FPC}{$mode objfpc}{$h+}{$endif}
> > {$ifdef mswindows}{$apptype console}{$endif}
> > uses
> > {$ifdef FPC}{$ifdef
On Thursday 24 September 2015 09:00:47 Michael Van Canneyt wrote:
> > produces the file json.rsj
> > "
> > {"version":1,"strings":[
> > {"hash":7200948,"name":"json.a","value":"a\u00C3\u00A4\u00C3\u0084"}
> > ]}
> > "
> > Is this intended? How can translation tools know that the Unicode points
> >
On Thursday 24 September 2015 09:28:28 Jonas Maebe wrote:
>
>
> > Should I make a bug report?
>
> There is already a (very old) bug report for that.
>
I meant a bug report for the unusual json format.
Martin
___
fpc-pascal maillist -
On Thursday 24 September 2015 09:46:06 Michael Van Canneyt wrote:
> On Thu, 24 Sep 2015, Martin Schreiber wrote:
> > On Thursday 24 September 2015 09:28:28 Jonas Maebe wrote:
> >>> Should I make a bug report?
> >>
> >> There is already a (very old) bug report for that.
> >
> > I meant a bug report
On Thursday 24 September 2015 09:59:49 Graeme Geldenhuys wrote:
> On 2015-09-24 08:14, Martin Schreiber wrote:
> >> > What did you expect to see ?
> >
> > "
> > {"version":1,"strings":[
> > {"hash":7200948,"name":"json.a","value":"a\u00E4\u00C4"}
> > ]}
> > "
>
> I would have expected the same as
On 24.09.2015 09:22, Graeme Geldenhuys wrote:
> On 2015-09-24 09:09, Martin Schreiber wrote:
>> It is an advantage to have pure ASCII files for such data.
>
>
> Escaped text seems optional, but the UTF-8 encoding seem recommended.
> Using non-escaped Unicode text is faster to parse and easier to
On 2015-09-24 14:48, Bo Berglund wrote:
> Does FPC recognize the Lazarus project file such that paths etc are
> observed?
No, FPC knows nothing about Lazarus project files. In Lazarus IDE you
can go to Project Options, and then click on the "Show Options" button
and the bottom of that dialog.
I want to check my options regarding Lazarus and FPC.
If I develop a program on Windows Lazarus, move it to Debian Lazarus
(x86) and then finally want to compile on ARM on for example Raspberry
Pi but outside of Lazarus, how is that done?
Does FPC recognize the Lazarus project file such that
On 2015-09-24 13:06, Michael Van Canneyt wrote:
> That's a bug (missing jsoDateTimeAsString in destreamer),
> please report it in the bugtracker.
OK, but against which version of FPC?
Regards,
- Graeme -
--
fpGUI Toolkit - a cross-platform GUI toolkit using Free Pascal
In our previous episode, Graeme Geldenhuys said:
> No, FPC knows nothing about Lazarus project files. In Lazarus IDE you
> can go to Project Options, and then click on the "Show Options" button
> and the bottom of that dialog. Copy and paste that into a shell script
> which you can then run.
>
>
lazbuild has option "--add-package"
W dniu 2015-09-24 o 16:09, Graeme Geldenhuys pisze:
On 2015-09-24 15:03, Marco van de Voort wrote:
Lazarus has lazbuild to simply compile a project from the commandline.
How is it going to know where to find packages if you haven't run the
Lazarus IDE and
On Thu, 24 Sep 2015, Graeme Geldenhuys wrote:
On 2015-09-24 15:03, Marco van de Voort wrote:
Lazarus has lazbuild to simply compile a project from the commandline.
How is it going to know where to find packages if you haven't run the
Lazarus IDE and loaded those packages at least once?
On 2015-09-24 15:32, Michael Van Canneyt wrote:
>> > OK, but against which version of FPC?
> Trunk.
Does that mean the upcoming FPC 3.0 will not contain a fix?
Anyway, filed as:
http://mantis.freepascal.org/view.php?id=28721
Regards,
- Graeme -
--
fpGUI Toolkit - a cross-platform GUI
On 09/24/2015 10:03 AM, Marco van de Voort wrote:
In our previous episode, Graeme Geldenhuys said:
No, FPC knows nothing about Lazarus project files. In Lazarus IDE you
can go to Project Options, and then click on the "Show Options" button
and the bottom of that dialog. Copy and paste that
On 2015-09-24 15:03, Marco van de Voort wrote:
> Lazarus has lazbuild to simply compile a project from the commandline.
How is it going to know where to find packages if you haven't run the
Lazarus IDE and loaded those packages at least once? I'm thinking in
terms of a headless build-server.
On Thu, 24 Sep 2015, Graeme Geldenhuys wrote:
On 2015-09-24 13:06, Michael Van Canneyt wrote:
That's a bug (missing jsoDateTimeAsString in destreamer),
please report it in the bugtracker.
OK, but against which version of FPC?
Trunk.
Michael.
On 09/24/2015 09:48 AM, Bo Berglund wrote:
I want to check my options regarding Lazarus and FPC.
If I develop a program on Windows Lazarus, move it to Debian Lazarus
(x86) and then finally want to compile on ARM on for example Raspberry
Pi but outside of Lazarus, how is that done?
the lpr
On 09/24/2015 11:14 AM, Michael Van Canneyt wrote:
On Thu, 24 Sep 2015, waldo kitty wrote:
On 09/24/2015 10:03 AM, Marco van de Voort wrote:
Lazarus has lazbuild to simply compile a project from the commandline.
but you have to have lazarus which is not available for all environments...
eg:
On Thu, 24 Sep 2015, waldo kitty wrote:
On 09/24/2015 10:03 AM, Marco van de Voort wrote:
In our previous episode, Graeme Geldenhuys said:
No, FPC knows nothing about Lazarus project files. In Lazarus IDE you
can go to Project Options, and then click on the "Show Options" button
and the
On 2015-09-24 16:14, Michael Van Canneyt wrote:
> Since the projects in question are lazarus projects to begin with, this is a
> non-issue.
Yes for LCL based apps. If I had to be technical... Lazarus IDE can
"manage" other non-LCL apps too, and those can include packages etc etc.
So you still
Rather than going down the lazbuild path as others have suggested, you
might want to think about fpcmake and creating a "Makefile.fpc" for your
project. That should be the standard way of building a lazarus project
just using fpc.
You will need to write a Makefile.fpc that does the same job
I tried sending this message two days ago, but it seems not to have gone
through. Trying again.
I like using include files, to break up big units into multiple files,
and also as macro-based templates.
One thing I do frequently is to put both the interface and the
implementation into one
Am 24.09.2015 18:00 schrieb "Tony Whyman" :
>
> Rather than going down the lazbuild path as others have suggested, you
might want to think about fpcmake and creating a "Makefile.fpc" for your
project. That should be the standard way of building a lazarus project
On Thu, 24 Sep 2015 16:21:31 +0100
Graeme Geldenhuys wrote:
> On 2015-09-24 16:14, Michael Van Canneyt wrote:
> > Since the projects in question are lazarus projects to begin with, this is
> > a non-issue.
>
> Yes for LCL based apps. If I had to be technical...
On Thu, 24 Sep 2015 09:48:32 -0400, Bo Berglund
wrote:
>I want to check my options regarding Lazarus and FPC.
>
>If I develop a program on Windows Lazarus, move it to Debian Lazarus
>(x86) and then finally want to compile on ARM on for example Raspberry
>Pi but outside of
On Friday 25 September 2015 03:52:25 Bo Berglund wrote:
> On Thu, 24 Sep 2015 09:48:32 -0400, Bo Berglund
>
> wrote:
> >I want to check my options regarding Lazarus and FPC.
> >
> >If I develop a program on Windows Lazarus, move it to Debian Lazarus
> >(x86) and then
41 matches
Mail list logo