From: Jim Rogers <jrogers@omnitech.com>
Subject: Re: Microsoft is turning VB in to C++
Date: 2000/02/17
Date: 2000-02-17T00:00:00+00:00 [thread overview]
Message-ID: <88h19v$5em$1@nnrp1.deja.com> (raw)
In-Reply-To: XhAq4.1061$4W1.104889@news4.usenetserver.com
In article <XhAq4.1061$4W1.104889@news4.usenetserver.com>,
"David Botton" <David@Botton.com> wrote:
> Microsoft is turning VB in to C++
> http://msdn.microsoft.com/vstudio/nextgen/language.asp
>
>
The documented OOP extensions of Visual Basic certainly look a lot like
C++. The place the really fall on their faces is their view of
concurrency. They define "Free Threads". "Free Threads" appear to
be little concurrent chunks that must execute completely
asynchronously from the rest of the code. There does not seem to be
any equivalent to a Rendezvous, or even mutually exclusive access to
shared memory.
--
Jim Rogers
Colorado Springs, Colorado USA
Sent via Deja.com http://www.deja.com/
Before you buy.
next prev parent reply other threads:[~2000-02-17 0:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-02-16 0:00 Microsoft is turning VB in to C++ David Botton
2000-02-17 0:00 ` Jim Rogers [this message]
2000-02-17 0:00 ` Pascal Obry
replies disabled
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox