BorlandTalk.com Forum Index BorlandTalk.com
Borland discussion newsgroups
 
Archives   FAQFAQ   SearchSearch   MemberlistMemberlist   UsergroupsUsergroups   RegisterRegister 
 ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 

Delphi on Win/64 sighting

 
Post new topic   Reply to topic    BorlandTalk.com Forum Index -> Delphi Non-Technical
View previous topic :: View next topic  
Author Message
Dennis Landi
Guest





PostPosted: Sat Dec 25, 2004 12:31 pm    Post subject: Delphi on Win/64 sighting Reply with quote



Headlines:

Delphi Developer would like a native Delphi for Win64 compiler but doesn't
even bother to ask. (I wonder why.)

http://blogs.slcdug.org/rhordijk/archive/2004/12/22/738.aspx

-- d
---------------------------------------------------
Need to see what's happening?
Check out the Delphi Community Blog Aggregator
http://delphi.flashblogger.com


Back to top
Ronald Hordijk
Guest





PostPosted: Mon Dec 27, 2004 10:36 am    Post subject: Re: Delphi on Win/64 sighting Reply with quote



The reason I did not ask for for a native compiler is because I agree with
borland that there are more important features. Five more to be precise, you
can read the in my blog:
http://blogs.slcdug.org/rhordijk/archive/2004/12/27/748.aspx

Ronald

"Dennis Landi" <nada (AT) nada (DOT) com> schreef in bericht
news:41cd5e0f (AT) newsgroups (DOT) borland.com...
Quote:
Headlines:

Delphi Developer would like a native Delphi for Win64 compiler but doesn't
even bother to ask. (I wonder why.)

http://blogs.slcdug.org/rhordijk/archive/2004/12/22/738.aspx

-- d
---------------------------------------------------
Need to see what's happening?
Check out the Delphi Community Blog Aggregator
http://delphi.flashblogger.com





Back to top
RandomAccess
Guest





PostPosted: Mon Dec 27, 2004 11:41 am    Post subject: Re: Delphi on Win/64 sighting Reply with quote



Some thoughts :

Add people to compiler team.
=====================
In our experience, throwing more people into development
rarely (actually for us NEVER) helped much. Sure you might get more
done if you're lucky, but new issues arise from implementing
such a strategy. We've found that quality suffered the most.
For us, the tighter the team, the better the output.
Just finding the right people is problematic and takes time away from
programmers.

Add more NET language features to Win32.
==============================
"....And when somebody want managed memory, he can write his own memory
manager."

Well, Delphi is a RAD system, is it not? I don't see many of us capable
of, or wanting to
writing a memory manager. I might be able to do it (if I'm lucky), but
would never want to.


NET 2.0 Support
============
There's no way out of this. Borland have chosen to support NET and the
sooner
they do it the better. I'm not a NET developer myself, but it seems
obvious to me
that since Borland have started on this track, it surely (and quite
rightly) must be a
priority for them.

I know that if I need to one day port my Win32 app to NET, I want Borland's
NET related code and cross compiler code to be as good as possible. I just
don't see
Borland doing any more work on Win32 in Delphi as productive for them.
Win64 is another matter, but isn't related to this post.


Multi-Threading support
=================
On the subject of better threading support for Win32.
I've done some multi-threading work and I can only say it's just plain
difficult at times.
I'm wondering exactly what you think Borland should do to improve the
situation because many issues have nothing to do with Delphi at all.

They could make more of the VCL thread safe, but outside of that what else
could they do?
Your blog mentions absolutely no specifics about what exactly you want, so
I wonder why
you wrote this in the first place.

best regards


best regards


Back to top
Arthur Hoornweg
Guest





PostPosted: Mon Dec 27, 2004 2:43 pm    Post subject: Re: Delphi on Win/64 sighting Reply with quote

Ronald Hordijk wrote:

Quote:
The reason I did not ask for for a native compiler is because I agree with
borland that there are more important features. Five more to be precise, you
can read the in my blog:


For me there's only one thing that I really need *now* and
that's good unicode support for Win32. Our current projects
will also be used in countries that use Arabic and Kyrillic
alphabets.

The past few months I had to carefully strip a huge
32-bit project from all Borland VCL components and now
use LMD Elpack components instead. Not a fun thing
to do.






--
Arthur Hoornweg

(In order to reply per e-mail, please just remove the ".net"
from my e-mail address. Leave the rest of the address intact
including the "antispam" part. I had to take this measure to
counteract unsollicited mail.)

Back to top
Andrew Rybenkov
Guest





PostPosted: Mon Dec 27, 2004 4:10 pm    Post subject: Re: Delphi on Win/64 sighting Reply with quote

Quote:
Not a fun thing to do.

though it's a fun when done.


--
Andrew Rybenkov.




Back to top
Arthur Hoornweg
Guest





PostPosted: Thu Dec 30, 2004 2:50 pm    Post subject: Re: Delphi on Win/64 sighting Reply with quote

Andrew Rybenkov wrote:

Quote:
though it's a fun when done.

Yes, but in the process I've found a dozen serious bugs in
Elpack. The developer team was very quick in fixing them,
though.

Still one thing won't work as advertized and that's the use
of right-to-left (arabic/persian) Unicode editing under Win98.





--
Arthur Hoornweg

(In order to reply per e-mail, please just remove the ".net"
from my e-mail address. Leave the rest of the address intact
including the "antispam" part. I had to take this measure to
counteract unsollicited mail.)

Back to top
Andrew Rybenkov
Guest





PostPosted: Fri Dec 31, 2004 7:56 pm    Post subject: Re: Delphi on Win/64 sighting Reply with quote

Quote:
Yes, but in the process I've found a dozen serious bugs in
Elpack. The developer team was very quick in fixing them,
though.

Still one thing won't work as advertized and that's the use
of right-to-left (arabic/persian) Unicode editing under Win98.


Well, what I meant about fun - total abandoning of VCL (as well as any other
3-rd party GUI lib).

Of course, if someone write a "make-and-forget" program those libs are ok.
But if your software should evolve, the best you can it's to limit interactions with OS to minimum.

It's not a fun to write most things yourself, but once it's done - you are most free software designer
in the world Wink -
you can port you program(s) to other OS in matter of few days; you do not care what Win versions your
customers run, because your software run under even Win95 (and in the same time it is not limited with
that OS limitations).

In the same stream, do not use "uncommon" language feautures, - like properties or interfaces in Delphi,
or multiple inheritence in C++, - thus you will not be locked to a particular vendor and/or language.

Once you adopt "Ascetic Programming" you will see that many problems are not problems at all.
(Particularly that right-to-left "problem" - let for MS that would be a problem - for you - it's just drawing
font glyphs on memory bitmap from right to left, and blitting the bitmap to screen - much easier that fighting
with next quirk of next OS version)


--
Andrew Rybenkov.






Back to top
Display posts from previous:   
Post new topic   Reply to topic    BorlandTalk.com Forum Index -> Delphi Non-Technical All times are GMT
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum


Powered by phpBB © 2001, 2006 phpBB Group
SEO toolkit © 2004-2006 webmedic.