Why I like VB.NET

[Sjoerd Verweij]

> Actually, they went out of their way to make C *easily* readable by
computer
> (parser).

Is that why there are so many single-pass C++ compilers out there? :-)

[Steve Dee]

Joe

> Does this help avoid the boolean property reference problem sometimes
> seen in VBA?

I'm not very familiar with VBA. What is the problem you are talking about?

[Steve Dee]

Patrick,

> "Deck stacked against you" is an overstatement. My point is that C's
authors'
> went out of their way to make C unreadable.

I really don't think that was the case and I don't find it unreadable at
all. But I know C, so I can "C" your point.

> The problem is that C-style syntax is needlessly unintuitive. Or to put it
> another way, it's inefficient.

Matter of opinion I guess.

> Not really. In C#, you've got one nest for the namespace, another for the
> class, another for the routine. OK, that's 3 levels of nesting before I
even
> start writing real code.

That shouldn't effect your loops should it?

> K&R? I'm not familiar with that term.

You better duck and cover for that question.....Kernignhan and
Ritchie....the creators of C.

The K&R curly brace style is like:
if (x == 1) {
....stuff
}

It really hasn't been very popular for many years. The following style is
what I use, and apparently the most popular for that matter:

if (x == 1)
{
.......stuff
}

[Steve Dee]

Bill,
dang that "Kill Joy"! I should have known it was a Java conspiracy .
I learned it that way myself, straight from the bible. I was beaten about
the neck and head over it though at different jobs and settled on the:
if (x == 1)
{
....stuff
}

style. Turns out that is still the most popular style for C. I never
really missed K&R once I got use to a new style (see I didn't ALWAYS write
the standards for the places I've worked!

[William Cleveland]

Steve Dee wrote:
>
> Bill,
> dang that "Kill Joy"! I should have known it was a Java conspiracy .
> I learned it that way myself, straight from the bible. I was beaten about
> the neck and head over it though at different jobs and settled on the:
> if (x == 1)
> {
> ...stuff
> }
>
> style. Turns out that is still the most popular style for C. I never
> really missed K&R once I got use to a new style (see I didn't ALWAYS write
> the standards for the places I've worked!

My C style (PostScript, too) isn't precisely consistent, but I think
it looks good and isn't confusing.

// Indent the braces for everything, except the function as a whole.
AFunction()
{
stuff;
stuff;
if (ABoolean)
{
ConditionalStuff;
ConditionalStuff;
}
}


I think I picked that up from the way I was taught to do Begin and End
in Pascal.

Bill

[Joe \Nuke Me Xemu\ Foster]

"Steve Dee" <Steve_Dee@md.prestige.net> wrote in message <news:3aa5b0d1@news.devx.com>...

> Joe
>
> > Does this help avoid the boolean property reference problem sometimes
> > seen in VBA?
>
> I'm not very familiar with VBA. What is the problem you are talking about?

See the Addendum at the end of http://www.mvps.org/access/bugs/bugs0005.htm

--
Joe Foster <mailto:jfoster@ricochet.net> On the cans? <http://www.xenu.net/>
WARNING: I cannot be held responsible for the above They're coming to
because my cats have apparently learned to type. take me away, ha ha!

[Steve Dee]

Bill,
Your style was my "second" style. That's the job where I got beat up
over K&R. I switched to my current style on the third job and have since
stuck with it, and "risen" to the point where I write the standards. I
prefer your current style over K&R still.

[Steve Dee]

Joe,
that's a weird one. It might help, but I doubt it. Then again I don't
know. The paren's would "force" an evaluation so it might work. It looks
like what is happening is VBA is creating a "hidden" reference to the
control which is not being released (set to Nothing). Interesting feature.

[Sjoerd Verweij]

> Your style was my "second" style. That's the job where I got beat up
> over K&R. I switched to my current style on the third job and have since
> stuck with it, and "risen" to the point where I write the standards. I
> prefer your current style over K&R still.

Remind me not to work for you... with my

function foo()
{
if (x == 1)
{
bar();
}
}

but then again, I have my editor at 9pt Verdana :-)

[David Bayley]

Sjoerd,

> Remind me not to work for you... with my
>
> function foo()
> {
> if (x == 1)
> {
> bar();
> }
> }
>

Oh, yuck! Of all the bracing styles, that's the one I dislike the most.
K&R works for me.

> but then again, I have my editor at 9pt Verdana :-)

But it's nice to see I'm not the only one using 9pt Verdana!
Non-proportional fonts suck... rah-rah-rah <g>.

Now, If We Can Just Get Rid Of Your PascalCased Variable Names ;-)

--
David.

[John Proffitt]

"Steve Dee" <Steve_Dee@md.prestige.net> wrote:
>Joe,
> that's a weird one. It might help, but I doubt it. Then again I don't
>know. The paren's would "force" an evaluation so it might work. It looks
>like what is happening is VBA is creating a "hidden" reference to the
>control which is not being released (set to Nothing). Interesting feature.
>
>

Do you think it might be a default property problem? Evaluating the Object
instead of the Boolean?

[Sjoerd Verweij]

> Now, If We Can Just Get Rid Of Your PascalCased Variable Names ;-)

Hey, it's always better what the average <censored> does on SQL server. Let
me look up some stuff:

REFERRED_TO__9___ (I kid ye not)
VW_MM_CONDATE_MAX
SP_EEFD_Numerator2
sp_DropEXTCreateDEL

And this is just in one database.

[Joe \Nuke Me Xemu\ Foster]

"John Proffitt" <bogon@earthlink.net> wrote in message <news:3aa863ec$1@news.devx.com>..

> "Steve Dee" <Steve_Dee@md.prestige.net> wrote:
> >Joe,
> > that's a weird one. It might help, but I doubt it. Then again I don't
> >know. The paren's would "force" an evaluation so it might work. It looks
> >like what is happening is VBA is creating a "hidden" reference to the
> >control which is not being released (set to Nothing). Interesting feature.
> >
> >
>
> Do you think it might be a default property problem? Evaluating the Object
> instead of the Boolean?

I think that's it. If the If gets an object, it ups the refcount when
evaluating the default property and forgets to decrease it again.

Is comparing with False better or faster than passing it through CBool?
Or might CBool also leak?

--
Joe Foster <mailto:jfoster@ricochet.net> Got Thetans? <http://www.xenu.net/>
WARNING: I cannot be held responsible for the above They're coming to
because my cats have apparently learned to type. take me away, ha ha!

[Steve Dee]

Sjoerd,
DON'T WORK FOR ME!!! There, I reminded you....I did the same style as
you are using in a previous life.
Hahaha.

"Sjoerd Verweij" <nospam.sjoerd@sjoerd.org> wrote in message
news:3aa7d39e$1@news.devx.com...
> > Your style was my "second" style. That's the job where I got beat
up
> > over K&R. I switched to my current style on the third job and have
since
> > stuck with it, and "risen" to the point where I write the standards. I
> > prefer your current style over K&R still.
>
> Remind me not to work for you... with my
>
> function foo()
> {
> if (x == 1)
> {
> bar();
> }
> }
>
> but then again, I have my editor at 9pt Verdana :-)
>
>
>
>

[Sjoerd Verweij]

> DON'T WORK FOR ME!!! There, I reminded you...

Noted :-)