TOPIC:

I just notes then compiler for CT640 produce strange messages. Check the screen layout.

Message example:

classsboffergetter.pas(537,88) Hint: Call to subroutine "ParseXMLRule(TXMLDocument;TDOMNode;TFavClsEvent);" marked as inline is not inlined


This function is for sure not inlined, and CT 600 and bellow do not produce this message.

I want to suggest that you do not use latest fpc trunk for your releases.
For me as developer It will be better that you use latest stable fpc sources.

I think fpc source is in progress of big change to implement string encoding like Delphi have, and therefore there are lot of bugs because RTL is not completely checked and adjusted.

Practically speaking. The CT tool is great and save lots of time comparing to install lazarus and all needed addons, and cross compile support is great, and so on and on...
But (somebody said the you can neglect everything before But ), you can not actually produce working and stable applications with such fpc trunk approach that CT have.

I now this is old story, but please reconsider this request once more.

Regards, Dinko

> I want to suggest that you do not use latest fpc trunk for your releases.

@Sternas: My 0,001 cent... One of the reason of the success of CodeTyphon is that it gives trunck of fpc.
What is also great with CT is that a binary version of "stable-fpc" is included in CT and used to compile fpc trunck.

The proposition is this:

Why CT does not give access to those "stable-fpc-binary-for-installation" after installing CT ?

All is already there, you do not have to add anything in CT.
At installation, CT uses a zip from /CodeTyphonIns/installbin/allzips/binfpc (the "stable-fpc").

The idea is to NOT delete that unzipped fpc-stable-files after installation and give the opportunity to people to use that "stable fpc" too.

So, to resume, CT should give the opportunity to use or fpc-trunck or fpc-stable (the one from /allzips/binfpc).

Fre;D

Guys Thanks

1) Before every CT release (and Lab release) we test and test many of 1500+ samples of CodeOcean
in ALL Host CPU-OS-Platform

2) We (all LAB programmers and LAB friends) don't believe in "Stable" and "Develop" programming theory

3) "Stock" FPC is NOT the same with CodeTyphon FPC (ctFPC) info
for sample in LAB CT 6.5 ctFPC use "fpc.cnf" file and NOT "fpc.cfg" like "Stock" FPC

4) Files xxx-xxx_bootstrap.7z file in codetyphon\allzips\binfpc\ directory
are NOT "stable-FPC" are bootstrap FPC compiler from FPC 3.0.2 or FPC 3.0.4
CT user can use these files in case that FPC 3.1.1 bootstrap compiler can't build the latest compiler from source.
Yes CT can build ctFPC
so
xxx-xxx.7z files in the same directory are FPC 3.1.1 trunk bootstrap compiler files

Normally CodeTyphon use ctFPC 3.1.1 trunk executable as bootstrap compiler
"Stock" FPC NOT

5) My friend @Dinko a compiler Hint: Call to subroutine "ParseXMLRule......
it's an Hint not an ERROR or problem

and Last my friends,
CodeTyphon Studio has very clear Philosophy
and
this must be acceptable from CodeTyphon Users

I expected answer which you gave

In that case I propose that you extend your tests to cover some UTC string situations.
There is no way that you can compile any database, xml, json application and expect to run correctly in some international environment.
So far there every CT had some issues:
Postgres 64 float was misrepresented as 10000 times bigger number,
wrongly utf encoded string caused application to hangs,
gzip function did not gzip big texts,
indy http server lose some memory, etc..

When I receive new CT version first I try to compile my test programs. My test programs for CT640 pass OK, so I put applications in our staging environment. After 7 days things start to happen.

I visually detected that almost all international characters are wrongly represented in GUI applications.
I tried to fix it, but it is impossible because it is deep in fpc and rtl.
Even fpc guys told that not all rtl functions are adjusted.
Who knows when it will be...

I think, I need to wait for the version which will cover my needs.
Actually CT600 have all the things that I need, but I want to be up to date (I skipped CT610, CT620, CT630). Btw CT630 have the same problem as CT640.

As you want my friend