So, what about the compiler?

So, what about the compiler?

Post by Saulo I. R » Sat, 05 Jun 2004 08:28:46


"Paul Dolen" < XXXX@XXXXX.COM > escreveu na mensagem


Welcome to Planet Earth :)

May be you would be interested in reading some recent posts in this NG!

All your questions will be answered in an upcoming, and undetermined, future
Open Letter by Borland.

It's the revival of the Open Letter Saga!

Saulo
 
 
 

So, what about the compiler?

Post by Paul Dole » Sat, 05 Jun 2004 08:29:31

I hadn't heard that much about the fabled new Borland compiler. If I
recall correctly, a beta version comes with CBX, no? I guess its all
speculation as to what will ever see the light of day as nothing seems
very certain right now. But, for people who have tried it out, how's
it looking? Is it looking like it might yet be a viable competitor to
VC++? Anybody have the slightest clue as to whether it is still being
worked on?

 
 
 

So, what about the compiler?

Post by Paul Dole » Sat, 05 Jun 2004 09:04:55

>All your questions will be answered in an upcoming, and undetermined, future

Yeah, I know we are all waiting on the open letter. What I was
wondering about is for one, what do people thing about the beta
compiler who have used it? And I guess I was asking for speculation
about what might be in the open letter about the compiler. But, sure,
some open letter speculation and $5 will get you coffee at
Starbucks...
 
 
 

So, what about the compiler?

Post by Adam Verst » Sat, 05 Jun 2004 09:33:24


Yeah, AFAIK a 'preview' could be downloaded for CBX. I never tried it myself
though so I can't be sure.

The thing is, its hard to speculate as to whether it has a chance of
competing against MS's compiler given its 'preview' nature. No has any idea
whatsoever as to what Borland is going to offer, whats its going to be like
and when it might surface.

IMO unless Borland come out with something dazzlingly impressive on the
compiler front, MS will win any compiler wars hands down. If Borland brings
out something that is only 'as good' as the MS compiler, past experience has
shown that it will stay that way.

This isn't a huge deal for me, I don't need the best optimising compiler
thats the most standards compliant. I just need a compiler that gets the job
done, and makes it easier on me to get the job done.

--
Vesty.
 
 
 

So, what about the compiler?

Post by Boian Mito » Sat, 05 Jun 2004 16:08:14


I don't think EDG does support managed extensions, and using ME is
not the best way to go. Even M$ is switching away from ME for the next
release of VC++.
 
 
 

So, what about the compiler?

Post by BigSte » Sat, 05 Jun 2004 16:13:23

Well, Borland's new compiler uses the EDG front end, so standards compliance
is a given (for e.g. template export is supported).
But the preview has optimisations disabled, and it doesn't support managed
extensions (which VC7.1 does).
Who knows what the release version will look like?
We'll have to wait...and wait...

Stew
 
 
 

So, what about the compiler?

Post by Boian Mito » Sat, 05 Jun 2004 16:25:04


There is no need to support ME. Even M$ regrets they did. You should
not support them. They are most likely a dead end. Instead you natively
support .NET within the C++, as M$ is doing for the next version.
 
 
 

So, what about the compiler?

Post by BigSte » Sat, 05 Jun 2004 16:29:23

Re-read my post - I typed "and it doesn't support managed extensions (which
VC7.1 does)."

Stew
 
 
 

So, what about the compiler?

Post by Russell Hi » Sat, 05 Jun 2004 16:35:17


It also uses DinkumWare for the STL as does VC++. In some quick tests I
did with it, things in boost that don't work (such as lambda and the
preferred function syntax) work with the new compiler. It also supports
(or will do if they ever release a full version) export which I read on
a MSFT FAQ that they currently don't have plans to implement.

So this is something they will have over Microsoft. I guess if they go
for .Net support with it, they will go to C++/CLI, not MC++ which as
I've just started playing with MC++, would be a good thing as MC++ as it
is, isn't good. (Well not when your trying to mix natively compiled code
with managed C++ code in the same app anyway).

Cheers

Russell
 
 
 

So, what about the compiler?

Post by Peter Agri » Sat, 05 Jun 2004 18:12:08


How is this supposed to go working? The syntax will change, they even change
the name of ME to C++/CLI but it still are managed extensions. They only
promissed it will have better interoperability with std C++. But how is this
going to work? Do you have details or a link?


Peter
 
 
 

So, what about the compiler?

Post by Pete Frase » Sat, 05 Jun 2004 18:59:21

MS have been talking to the C++ standards people and seem to be able to get
them to modify the next std to cope with C++/CLI extensions. This means that
they could be in other people's future compilers.
The changes were also to address people's concerns about C++/Managed and
looked good when Herb Sutter showed them at the ACCU 2004 conference.
You can now delete when you want(if you've new'd properly), amongst other
things.
Rgds Pete




change
this
 
 
 

So, what about the compiler?

Post by Don Ki » Sat, 05 Jun 2004 20:09:51

> How is this supposed to go working? The syntax will change, they even
change
this

On the Visual C++ .Net homepage: http://www.yqcomputer.com/

Click the link under "Multimedia" for Herb Sutter's webcast of how CLI will
fully interoperate with Std C++.

He does a pretty good job of explaining it.

-Don
 
 
 

So, what about the compiler?

Post by Boian Mito » Sun, 06 Jun 2004 02:06:41


My information is a first hand from one of the M$ C++ project
managers. They ware very unhappy with the Managed Extensions. They are
C++ folks after all.