Re: IMMEDIATE WINDOW in VB7 (was: Transition from Visual Basic 6.0 to Visual Basic.NET)

[Tim Romano]

I read that there was going to be a special version of the JITer for Windows
CE, that compiles only what is needed. Couldn't a wrapper be put around that
technology so that an Immediate Window could be based on it?

Tim Romano
www.aimsdata.com/tim



"John Proffitt" <bogon@earthlink.net> wrote in message
news:3a9736fe@news.devx.com...
>
> kylix_is@hotmail.com (Mike Mitchell) wrote:
> >On 23 Feb 2001 07:32:49 -0800, "Jim Pragit" <NoSpam@NoSpam.com> wrote:
> >>
> >>Being able to test a routine from the Immediate window without having to
> >>create a test program is a *huge* time saver. Please add this back in.
> >
> >They can't "add it back in". We're not talking about the next version
> >of VB6 here. VB.NET is a c-o-m-p-l-e-t-e-l-y new rewrite from the
> >ground up. There *is* nothing they could put it back into!
> >
>
> Maybe eventually they can hack together an interpreted version of the
runtime
> for debugging. The only problem would be to maintain cosistency with the
> regular compiler. How does VB6 do it?
>
> JBP
>

[Jonathan Allen]

Sounds reasonable to me. Another option is to simply run a variation of
VBScript in the immediate window.

--
Jonathan Allen

My Bigfoot email account was rejecting messages for no apparent reason.
Therefore I am now using greywolf@cts.com as my email address.



"Tim Romano" <tim_romano@yahoo.com> wrote in message
news:3a97dc5d$1@news.devx.com...
> I read that there was going to be a special version of the JITer for
Windows
> CE, that compiles only what is needed. Couldn't a wrapper be put around
that
> technology so that an Immediate Window could be based on it?
>
> Tim Romano
> www.aimsdata.com/tim
>
>
>
> "John Proffitt" <bogon@earthlink.net> wrote in message
> news:3a9736fe@news.devx.com...
> >
> > kylix_is@hotmail.com (Mike Mitchell) wrote:
> > >On 23 Feb 2001 07:32:49 -0800, "Jim Pragit" <NoSpam@NoSpam.com> wrote:
> > >>
> > >>Being able to test a routine from the Immediate window without having
to
> > >>create a test program is a *huge* time saver. Please add this back in.
> > >
> > >They can't "add it back in". We're not talking about the next version
> > >of VB6 here. VB.NET is a c-o-m-p-l-e-t-e-l-y new rewrite from the
> > >ground up. There *is* nothing they could put it back into!
> > >
> >
> > Maybe eventually they can hack together an interpreted version of the
> runtime
> > for debugging. The only problem would be to maintain cosistency with
the
> > regular compiler. How does VB6 do it?
> >
> > JBP
> >
>
>

[John Butler]

"Jonathan Allen" <greywolf@cts.com> wrote in message
news:3a9aae0e@news.devx.com...
> Sounds reasonable to me. Another option is to simply run a variation of
> VBScript in the immediate window.

They could do it but we're supposed to be learning C# now and/or purging
ourselves of the things we liked VB for aren't we..

<skulks off muttering>

[Ahmed Waheed]

Yup, I think that will definitely do the trick
>