Marco van de Voort kirjoitti tiistai 04 tammikuu 2011 17:57:43:
> > No, my whole idea is to modernize the code and NOT support old versions.
>
> And what if it doesn't work? That is the whole problem. You can't as with
> other versions first migrate the code to roughly work on the new delphi
> (fi
michael.vancann...@wisa.be kirjoitti tiistai 04 tammikuu 2011 15:08:01:
> Not so here. Off the top of my mind:
> - Explicit encodings run awry
> - Some Components that used explicit Windows DoSomeThingA calls no longer
> functioned. (TProcess for instance suffers)
> - Database fields change type.
>
On Tue, 4 Jan 2011 14:20:55 +0200, Juha Manninen wrote:
If I told to a Java programmer that Object Pascal features match Java
features, how would I prove it? By showing him the HTML component
code?
IFDEFs and self-made conversion funcs just to support different
string types.
The Java guy wo
In our previous episode, Juha Manninen said:
> >
> > I am in the process of converting a D7 application to a D2010 application.
> > There are lots of string encoding problems, and none of them is solved
> > "automatically".
>
> What kind of problems did you have?
First, D2009 only solves labelli
On 04 Jan 2011, at 13:20, Juha Manninen wrote:
The Java guy would ask if there is any common unicode string type. I
would say
"Not yet but it's coming, but we can't use it because we must
support the old
compiler versions".
Java's string type is roughly equivalent to FPC's UnicodeString:
On Tue, Jan 4, 2011 at 10:20 AM, Juha Manninen
> I would also laugh if I was the Java developer.
Then just wait until the guy needs to use an ifdef and ops. There
are no ifdefs in Java. Your turn to laugh has come as he tries to hack
around this very serious short coming.
--
Felipe Monteiro
On Tue, 4 Jan 2011, Juha Manninen wrote:
michael.vancann...@wisa.be kirjoitti tiistai 04 tammikuu 2011 12:42:44:
On Tue, 4 Jan 2011, Juha Manninen wrote:
This component would really benefit from the Delphi2009 default string
type. All string encoding problems would be solved automatically.
On 04 Jan 2011, at 11:36, Juha Manninen wrote:
Now a question: is there any idea when the new string is ready for
testing
and experimenting by application programmers?
No.
I understood there are some fundamental design problems that need to
be
solved.
I'm not aware of any fundamental
michael.vancann...@wisa.be kirjoitti tiistai 04 tammikuu 2011 12:42:44:
> On Tue, 4 Jan 2011, Juha Manninen wrote:
> > This component would really benefit from the Delphi2009 default string
> > type. All string encoding problems would be solved automatically.
>
> That is simply not correct.
>
> I
On Tue, 4 Jan 2011, Juha Manninen wrote:
There are now 2 projects working on the same HTML component, one is HtmlPort
by Phil Hess, one is HtmlViewer maintained in Google Code.
I am trying to figure out the right way to modernize the code.
There is an idea to support all string types in old De
There are now 2 projects working on the same HTML component, one is HtmlPort
by Phil Hess, one is HtmlViewer maintained in Google Code.
I am trying to figure out the right way to modernize the code.
There is an idea to support all string types in old Delphis and new Delphis
and 3rd party Delphi Uni
11 matches
Mail list logo
