[fpc-devel] OpenBSD compiler

2011-10-04 Thread Leonardo M . Ramé
Hi, I noted that Pierre is updating the OpenBSD port. 

Does anyone knows where can I find a bootstraping compiler for this platform?.
 
Leonardo M. Ramé
http://leonardorame.blogspot.com___
fpc-devel maillist  -  fpc-devel@lists.freepascal.org
http://lists.freepascal.org/mailman/listinfo/fpc-devel


Re: [fpc-devel] utf-8 package in Free Pascal

2011-10-04 Thread Michael Schnell

On 10/04/2011 01:02 PM, Hans-Peter Diettrich wrote:



I wonder when Lazarus will be able to follow and use this string type 
for the complete library.


The LCL will use one unique encoding, most probably UTF-8 as the only 
losless Unicode representation. This means that strings with different 
encoding are converted whenever passed to a control, or read from it.



This might be true and it is obviously the way to go when running on Linux.

But with dynamically encoded Strings, the LCL does not need to force a 
certain encoding on it's user code interface. It _could_ internally use 
UTF-8 on Linux and UTF-16 on Windows with the same source code (only 
some differences in the direct system API related code that is 
OS-specific anyway). In the user code auto-conversion is supposed to 
happen whenever necessary.


I suppose this would result in faster programs on Windows.

Of course auto-conversion in the user code might slow down certain 
programs hen the user somehow forces a certain coding. And inappropriate 
user code might implicitly rely on a certain internal coding of a string 
and work only on a certain OS.


-Michael
___
fpc-devel maillist  -  fpc-devel@lists.freepascal.org
http://lists.freepascal.org/mailman/listinfo/fpc-devel


Re: [fpc-devel] utf-8 package in Free Pascal

2011-10-04 Thread Hans-Peter Diettrich

Michael Schnell schrieb:

On 10/04/2011 10:59 AM, Michael Van Canneyt wrote:


Yes. Each string will have a codepage identifier associated with it.
if, during an assign operation, a difference exists, a conversion will 
occur.

(there are of course some exceptions)


GREAT !


Not really :-(

I wonder when Lazarus will be able to follow and use this string type 
for the complete library.


The LCL will use one unique encoding, most probably UTF-8 as the only 
losless Unicode representation. This means that strings with different 
encoding are converted whenever passed to a control, or read from it.


DoDi

___
fpc-devel maillist  -  fpc-devel@lists.freepascal.org
http://lists.freepascal.org/mailman/listinfo/fpc-devel


Re: [fpc-devel] utf-8 package in Free Pascal

2011-10-04 Thread Michael Schnell

On 10/04/2011 11:59 AM, Sven Barth wrote:


The earliest point is when the next big release after 2.6 is released 
(note: I don't mean 2.6.x here, more a 2.8). As 2.6 is currently 
prepared you can estimate how long that will take.



I see. ;-)

Unfortunately Delphi is way ahead on this behalf, but I also know that 
Delphi provides a lot of traps for users converting their "ANSI" 
projects to use NewStrings (even if they don't need Unicode at all).


-Michael
___
fpc-devel maillist  -  fpc-devel@lists.freepascal.org
http://lists.freepascal.org/mailman/listinfo/fpc-devel


Re: [fpc-devel] utf-8 package in Free Pascal

2011-10-04 Thread Sven Barth

Am 04.10.2011 11:19, schrieb Michael Schnell:

On 10/04/2011 10:59 AM, Michael Van Canneyt wrote:


Yes. Each string will have a codepage identifier associated with it.
if, during an assign operation, a difference exists, a conversion will
occur.
(there are of course some exceptions)


GREAT !

I wonder when Lazarus will be able to follow and use this string type
for the complete library.


The earliest point is when the next big release after 2.6 is released 
(note: I don't mean 2.6.x here, more a 2.8). As 2.6 is currently 
prepared you can estimate how long that will take.


Regards,
Sven
___
fpc-devel maillist  -  fpc-devel@lists.freepascal.org
http://lists.freepascal.org/mailman/listinfo/fpc-devel


Re: [fpc-devel] utf-8 package in Free Pascal

2011-10-04 Thread Michael Schnell

On 10/04/2011 10:59 AM, Michael Van Canneyt wrote:


Yes. Each string will have a codepage identifier associated with it.
if, during an assign operation, a difference exists, a conversion will 
occur.

(there are of course some exceptions)


GREAT !

I wonder when Lazarus will be able to follow and use this string type 
for the complete library.


-Michael
___
fpc-devel maillist  -  fpc-devel@lists.freepascal.org
http://lists.freepascal.org/mailman/listinfo/fpc-devel


Re: [fpc-devel] utf-8 package in Free Pascal

2011-10-04 Thread Michael Van Canneyt



On Tue, 4 Oct 2011, Michael Schnell wrote:


On 10/03/2011 11:41 AM, michael.vancann...@wisa.be wrote:



Currently, hard work is being put in the unicode string and codepage string
routines in the RTL.


Do I understand correctly that this is the "New String" string handling (to 
be optionally, by default or exclusively used) ?


Yes.

Do I understand correctly, that with theses strings automatic conversion 
between different string encodinge (e.g. locale based ANSI <-> Unicode and 
UTF-8 <> UTF-16) is provided in the RTL ?


Yes. Each string will have a codepage identifier associated with it.
if, during an assign operation, a difference exists, a conversion will occur.
(there are of course some exceptions)

Michael.
___
fpc-devel maillist  -  fpc-devel@lists.freepascal.org
http://lists.freepascal.org/mailman/listinfo/fpc-devel


Re: [fpc-devel] utf-8 package in Free Pascal

2011-10-04 Thread Michael Schnell

On 10/03/2011 11:41 AM, michael.vancann...@wisa.be wrote:



Currently, hard work is being put in the unicode string and codepage 
string

routines in the RTL.


Do I understand correctly that this is the "New String" string handling 
(to be optionally, by default or exclusively used) ?


Do I understand correctly, that with theses strings automatic conversion 
between different string encodinge (e.g. locale based ANSI <-> Unicode 
and UTF-8 <> UTF-16) is provided in the RTL ?


-Michael
___
fpc-devel maillist  -  fpc-devel@lists.freepascal.org
http://lists.freepascal.org/mailman/listinfo/fpc-devel


RE: [fpc-devel] New Windows gdb-binary

2011-10-04 Thread Pierre Free Pascal


> -Message d'origine-
> De : fpc-devel-boun...@lists.freepascal.org [mailto:fpc-devel-
> boun...@lists.freepascal.org] De la part de Joost van der Sluis
> Envoyé : lundi 3 octobre 2011 16:24
> À : FPC developers' list
> Objet : Re: [fpc-devel] New Windows gdb-binary
> 
> On Sat, 2011-10-01 at 10:26 +0200, Florian Klämpfl wrote:
> > Am 30.09.2011 15:02, schrieb Joost van der Sluis:
> > > Please test this gdb-version, and tell me about your experiences.
> > > Especially Martin. ;)
> > >
> > > Oh, you can download it here:
> > > http://www.lazarussupport.com/gdb_lazarssupport_20110930.zip
> >
> > Did you get also a libgdb.a which you could provide for the fpc ide?
> 
> No. I don't know how to build a libgdb.a. I'll look into it later.

Loook at packages/gdbint/gen-gdblib-inc.sh script,
it should also work for mingw.

Pierre

___
fpc-devel maillist  -  fpc-devel@lists.freepascal.org
http://lists.freepascal.org/mailman/listinfo/fpc-devel


Re: [fpc-devel] utf-8 package in Free Pascal

2011-10-04 Thread michael . vancanneyt



On Tue, 4 Oct 2011, Alexander Klenin wrote:


On Tue, Oct 4, 2011 at 08:48, Michael Van Canneyt
 wrote:

There is, again, a continuum between careful development and stangation.
While acknowledging great work that FPC team has done on the former,
I'd venture to say that is came uncomfortably close to the latter.


I'd venture to disagree.

Attached is a small graph from the bugtracker activity.
As you can see, the bugfix rate remains constant, which refutes
'stagnation'. We do work, even if it is not so 'visible'.


As I said, I did not ever deny you work, of course you do.
Still, "steady bugfixing" and "dymanic evolution" are not quite the same,
although related.


Now, to counter the perception of stagnation, you can help:
Please help us working on fppkg


Looking at the bugtracker, I found a single non-assigned issue #18321,
which talks about some "webdesign" package I know nothing about.
So I where can I look at the todo-list?


Slowly, we (mainly Joost, in fact) are converting the FPC packages to this
new mechanism, fixing bugs as we go along. You can help by testing this, and
converting more packages to the new fppkg.


Perhaps I can take care of a single package -- for example, numlib improvement
was discussed recently on the forum. However, I am afraid my work will
be rejected again as was the case with fpdoc.


Basing an opinion on 1 occurrence - however painful - is not very scientific :-)

The amount of patches being rejected is a small minority. But yes, it sometimes
happens.


So I'd consider working on numlib (+ math unit, which is obviously
closely related),
if I'd get either commit access or somebody who will timely commit my patches.


You should contact Marco Van De Voort, he currently looks after numlib.

Michael.
___
fpc-devel maillist  -  fpc-devel@lists.freepascal.org
http://lists.freepascal.org/mailman/listinfo/fpc-devel


RE: [fpc-devel] New Windows gdb-binary

2011-10-04 Thread Pierre Free Pascal
> > Use this new macro:
> >
> > $ cvs diff -u -p  gdbtypes.h
> > Index: gdbtypes.h
> > ===
> > RCS file: /cvs/src/src/gdb/gdbtypes.h,v
> > retrieving revision 1.153
> > diff -u -p -r1.153 gdbtypes.h
> > --- gdbtypes.h  5 Jul 2011 13:36:41 -   1.153
> > +++ gdbtypes.h  3 Oct 2011 14:39:08 -
> > @@ -1115,6 +1115,11 @@ extern void allocate_gnat_aux_type (stru
> > || TYPE_NFN_FIELDS (thistype) == 0) \
> > && (TYPE_STUB (thistype) || !TYPE_STUB_SUPPORTED (thistype)))
> >
> > +/* A helper macro that returns the name of a type or "unnamed type" if
> the
> > type
> > +   has no name.  */
> > +#define TYPE_SAFE_NAME(type) \
> > +  (TYPE_NAME (type) ? TYPE_NAME (type) : _(""))
> > +
> >  /* A helper macro that returns the name of an error type.  If the type
> > has a name, it is used; otherwise, a default is used.  */
> >  #define TYPE_ERROR_NAME(type) \
> 
> roflol. Take a good look at this patch. Especially the last few
> lines...

  Of course I saw the TYPE_ERROR_NAME macro
and I adapted it because I believed that you
were using this in a case where the type itself was not
an error type.
 
> I'll use TYPE_ERROR_NAME. Thanks for the hint. ;)

  Again, it all depends if you only need it for
types that are already flagged as error type
(which has a precise meaning inside GDB).

  Pierre


___
fpc-devel maillist  -  fpc-devel@lists.freepascal.org
http://lists.freepascal.org/mailman/listinfo/fpc-devel