Board index » cppbuilder » Re: The Open Letter Day Arrived

Re: The Open Letter Day Arrived


2004-05-19 04:12:21 PM
cppbuilder9
Alisdair - you're back! Good to see you at ACCU.
Rgds Pete
"Alisdair Meredith" <alisdair.meredith@ XXXX@XXXXX.COM >
wrote in message news: XXXX@XXXXX.COM ...
Quote
Russell Hind wrote:
 
 

Re:Re: The Open Letter Day Arrived

Peter Agricola wrote:
Quote
Can we use C++ for cross platform development including .NET?
Not sure what you mean. In theory you can do that now anyway!
The MS C++ compiler has a switch to compile for .NET IL, and will
compile regular C++ to something that will run in the .NET environment.
Of course, you don't get any .NET services this way, no garbage
collection and no ability to call .NET APIs, but this is how the Quake2
port was done.
As for "portable .NET", the C++/CLI is going through the same ECMA
process that standardised the base .NET services, the 'CLS', which is
now an ISO standard as the basis for the .NET clones. It will then be
'fast-tracked' as an ISO standard, so several ISO comittee members are
quite active in the ECMA group, not just Microsoft! So yes, it should
be portable to any other compiler supporting the standard, and I hope
Borland will see enough interest to be one such vendor, although not at
the expense of getting an upgrade to BCB out. Hopefully they can
manage both though <g>(and No, I don't have any inside knowledge
about any updates yet either :? ( )
Quote
What is authoring for .NET and consuming it?
In VCL terms, the difference between using a component and authoring
one. Managed C++ simply had the goal off letting you use .NET APIs and
components, it is far from the nicest language to write .NET components
in.
C++/CLI makes C++ a natural choice for authoring .NET components too.
Imagine if your C++ VCL components could be used by Delphi too?
BCB/VCL is somewhere in the middle of this picture, where it is easy to
create components for other BCB users, but not for other VCL users in
general.
AlisdairM
 

Re:Re: The Open Letter Day Arrived

Russell Hind wrote:
Quote
Thanks Alisdair, that is what I was thinking. Good to see you back
with newsgroup access again!
Kind-of.
I only have access at home, but I'm getting home early enough to log in
again <g>
Quote
Just read this in CUJ.
I keep meaning to subscribe to that, but seeing the price triple for UK
postage hits my 'rip-off' gene, and my wallet stays shut. Is it worth
the UK subscription rate? Or have you found a more reasonable way of
obtaining it?
AlisdairM
 

{smallsort}

Re:Re: The Open Letter Day Arrived

Pete Fraser wrote:
Quote
Alisdair - you're back! Good to see you at ACCU.
Rgds Pete
Thanks. It's always good to catch up with old friends at the ACCU
(quick plug for anyone who can make it to the UK next year ;? )
Hopefully I will be able to get back from work early enough to maintain
a presence until work see fit to allow me through the firewall again.
AlisdairM
 

Re:Re: The Open Letter Day Arrived

"Alisdair Meredith" wrote:
Quote
The MS C++ compiler has a switch to compile for .NET IL, and will
compile regular C++ to something that will run in the .NET environment.
Of course, you don't get any .NET services this way, no garbage
collection
Good. I always clean up my own mess.
Quote
and no ability to call .NET APIs, but this is how the Quake2
port was done.
But for the interface it is still calling WIN32. For that I want to use
WinFX.
This will not be possible?
Quote
As for "portable .NET", the C++/CLI is going through the same ECMA
process that standardised the base .NET services, the 'CLS', which is
now an ISO standard as the basis for the .NET clones. It will then be
'fast-tracked' as an ISO standard, so several ISO comittee members are
quite active in the ECMA group, not just Microsoft!
I don't like the idea of another flavour of C++.
Quote
So yes, it should
be portable to any other compiler supporting the standard, and I hope
Borland will see enough interest to be one such vendor,
But when this compiler generates native code on multiple platforms we end up
with two incompatible source streams, making all the efforts for a std C++ a
waste.
Peter
 

Re:Re: The Open Letter Day Arrived

Alisdair Meredith wrote:
Quote

I keep meaning to subscribe to that, but seeing the price triple for UK
postage hits my 'rip-off' gene, and my wallet stays shut. Is it worth
the UK subscription rate? Or have you found a more reasonable way of
obtaining it?

Its just over double, current price form cuj.com is $65 (US is $30)
which I don't see as too bad for a years subscription. I think it is
worth it as I quite like the mag. Used to get C++ Report until it was
cancelled.
Cheers
Russell
 

Re:Re: The Open Letter Day Arrived

Harold Howe [TeamB] wrote:
Quote

>I can't understand why after 8 months, a week is not enough
>to write down that Open Letter and to publish it as planed
>and announced!

I agree that Borland's plan for the future of BCB should not
take 8 months to announce. However, the future has looked much
brighter for BCB this week than it did during the past half
year, thanks mostly to posts from Robert E. So what if Robert
is off on the timing of the letter? He is not the one writing
it. He thought it would be ready, but it isn't. So what? There
is nothing Robert can do to expedite the letter. Why beat him
and Borland up over it?

I think we should be grateful for the information we did receive
this week (some of which involved a calculated personal risk).
The information that Robert posted is valuable, but should not
be interpreted as official company statements. If people on this
group begin treating everything that Robert says as the
official, golden voice of Borland, then Borland is simply going
to ask Robert to stop posting altogether. I don't see how that
benefits any of us.

We have waited half a year, what's another week? If the letter
isn't released after another week or two, then I think we can
return to a state of frustration, despair, and anger. Until
then, we can spend our time arguing the finer points of what
constitutes an emulator and what doesn't.

H^2
Well, Howard, it looks like the one to two weeks is almost up and nothing
has happened. I agree that people should not give Robert E a hard time but
as far as Borland is concerned, they seem remarkably casual about the loss
of their reputation. If Borland was my company, I would have been a lot
more worried and would have would have considered it a number 1 priority to
isse a clear policy statement to BCB users months ago. If it was bad news,
then so be it (as long as I was convinced that the best interests of
Borland were being served - the company comes first, it has to - without
that there is nothing anyway). As it is many of the BCB users own
companies are being damaged; fewer customers would buy their applications
if the compiler VCL they are using has an unknown/uncertain future. The
lack of information stops these, often small, companies from planning
effective policy for the future.
The only way to slow the slide of a reputation is to make a concrete promise
and deliver - ON TIME. Then if you make another and stick to that, the
slide might stop. Then if you make several more and stick to those you
start the slow recovery toward a better reputation. Reputations take years
to gain and weeks/days to lose.
Maybe I am wrong and a really clear Open Letter will arrive in the next
couple of days which reassures the whole user base and is really credible.
Well I do sincerely hope so, as I have an application I plan to market in
the next few months and I don't know what is going to happen.
 

Re:Re: The Open Letter Day Arrived

On Mon, 24 May 2004 11:29:38 +0100, john blackburn wrote:
I have to concur that Borland are not doing themselves any favours here. It
is hard to understand why the new open letter has still not appeared unless
it's going to turn out to be dozens of pages long. Unfortunately this
recent problem is turning out to be a good example of why companies should
be more cautious about what they tell people.
It does little to encourage an "open house" policy and is certainly not
helping to foster credibility. I hope someone at Borland is learning
further lessons from this but without knowing what's going on inside it's
hard to know what lessons can be learnt.
--
Andrue Cope
[Bicester UK]
 

Re:Re: The Open Letter Day Arrived

Andrue Cope wrote:
Quote
Unfortunately this recent problem is turning out to be a good example
of why companies should be more cautious about what they tell people.
I beg to differ. What's hindering the release of the open letter seems
to be precisely the resistance to release information. And what's
causing problems is the fact that such an open letter is almost a year
late, precisely because of the hush-hush approach. It's not failure to
deliver features, or promised features that are causing the problem,
from the start, but an uncompromising lack of information.
--
Ken
planeta.terra.com.br/educacao/kencamargo/
* this is not a sig *
 

Re:Re: The Open Letter Day Arrived

Andrue Cope wrote:
Quote

I have to concur that Borland are not doing themselves any favours here. It
is hard to understand why the new open letter has still not appeared unless
it's going to turn out to be dozens of pages long. Unfortunately this
recent problem is turning out to be a good example of why companies should
be more cautious about what they tell people.

I've just been chatting to the people I used to work with, and they,
like us now, are considering the move to VS.Net, probably with a C#
interface and a C++ backend, purely because of the lack of direction and
confusing information from Borland.
The reason we moved to Borland at the last company was to get away from
a VB front-end and VC++ back-end but both places are now considering
moving back because of the current situation.
Maybe the new C++/CLI stuff in Whidbey (or what ever it is) will allow
for an entire C++ product as BCB does now, which will be good, because
I'm not keen on interfacing betwee two languages but its certainly being
considered.
Cheers
Russell
 

Re:Re: The Open Letter Day Arrived

Andrue Cope wrote:
Quote
It does little to encourage an "open house" policy and is certainly not
helping to foster credibility.
Exactly.
'Open house' policy? What open house policy? Other than the few random
comments by Robert E and others a couple of weeks back, info seems to have
all but dried up again. Then there's this promise of an open letter that is
supposedly going to come out this lifetime.
How is the current situation *any* different to what it was last year about
a week after the second open letter was first announced?
--
Vesty.
 

Re:Re: The Open Letter Day Arrived

"Russell Hind" wrote:
Quote
I've just been chatting to the people I used to work with, and they,
like us now, are considering the move to VS.Net,
Exactly. This is what Marketing/PR keeps telling inside Borland. If you wait
long enough, every problem solves itself! You just have to see it.
Peter
 

Re:Re: The Open Letter Day Arrived

On Mon, 24 May 2004 07:43:06 -0400, Adam Versteegen wrote:
Quote
How is the current situation *any* different to what it was last year about
a week after the second open letter was first announced?
I'm inclined to think it's worse, myself. We had just about come round to
the idea of BCB being dead and reconciling ourselves to moving somewhere
else and now...who knows?
The advantages of a BCB9 are for us sufficiently great that we would not
now consider any alternative. That leaves us completely at sea.
--
Andrue Cope
[Bicester UK]
 

Re:Re: The Open Letter Day Arrived

"Adam Versteegen" < XXXX@XXXXX.COM >wrote in message news:40b1dfc5$ XXXX@XXXXX.COM ...
Quote
How is the current situation *any* different to what it was last year about
a week after the second open letter was first announced?
I would have to say it's worse.
 

Re:Re: The Open Letter Day Arrived

After much cogitation, XXXX@XXXXX.COM says...
Quote

I would have to say it's worse.



Borland seems to have no problem with a roadmap for Microsoft, but they
can't give us any official indication of direction:
SAN DIEGO--(BUSINESS WIRE)--May 24, 2004-- Borland Software Corporation
(Nasdaq:BORL - News) today presented alongside Microsoft and leading
global systems integrators a Microsoft road map for delivering the
Microsoft Visual Studio 2005 Team System.