Re: Wish I was using .net

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance



Because it would have ruined the consistency of the language. I can
understand having an optional library you reference to get this
functionality or having a better import but having this as a default part of
the language would have polluted it.

Okay, this issue is dead for us -- you think it would pollute the
language but you would be ok with it being an optional library, which
would have most likely been an ok compromise from my point of view.
However, they didn't do it...and that right there is just one example
of how I think the designers of VB.Net (not .Net in general, just
VB.Net) had contempt and no full understanding of what VB code really
existed out in the world.

I don't really see how you can argue that, less typing is simply better for
professionals.

I think that is a very gray line -- yeah, I don't want to have to write
something like "a memory location that is 4 bytes long including a sign
bit", but dim x as integer vs. int x...that gets to be a little bit
gray. At what point does readability come into play? I mean, I don't
want an entire if block to be this: "Ix=1|c+|c-" -- I mean, that would
be even easier to TYPE than:
int x = 1;
int c = 0;

if(x==1)
{
c++;
}
else
{
c--;
}

Don't try to
tell me that because I prefer BASIC then I am a beginner. Typing "Dim
X as Inte" (then space) instead of int x doesn't slow me down at all.

It has to slow you down, at least to some degree.

It probably does, but that isn't where my big slowdowns come from. I
spend less time actually typing code than I do planning what I want to
do, I bet. I haven't performed some kind of videotaping test or
anything, but...

What object does the Abs function belong to?

the Math object.

I know that's what they tell people, but I've never bought this.
Static functions and things like what you call the Math "object" aren't
objects. They aren't instantiated, they simply exist. This is where
OO theory broke down in the real world implementation, so people
created this magic always instantiated object, that really isn't and
object, and patted themselves on the back because they stayed fully
object oriented (only they didn't -- they faked themselves out).

I'd be happy with an addin library or better import wizard but would prefer
not to have them available in the language. People will use them for new
projects and we'll never get rid of them.

Yes, some peole would. And they'd bitch and moan when it was removed.
However, peole like ME, who try to stay on top of these things because
it is my job, we would see the writing on the wall and take appropriate
steps to isolate that code if not outright change it. But we would be
PREPARED to rewrite certain areas of our apps or to encapsulate that
functionality in a DLL or whatever...and we wouldn't feel betrayed and
left out in the cold.

Really it's just part of the learning experience. Dotnet is pretty easy to
pick up from vb6 (except maybe ado:-) and will save you time in the future.

I am picking it up pretty easily -- there are days when I feel totally
comfortable about what I'm doing, and then there are days when I have
to relearn some kind of basic thing -- like adding items to a listbox.
Now you add OBJECTS into the listbox. That's great, but now I end up
making many classes or structures for things to add to the listbox
merely so I can create a ToString method so the listbox display looks
intelligent. Then I add in CType all over the place so that I can
actually USE the object in a selectedindexchanged event. Yes, there
are benefits to this. Yes there are cons to this, too.

All I was saying was Closing and Closed are the same as QueryUnload and
Unload but now you mention it the methods do match WM_CLOSE, although I'm
not sure what the other windows message is.

Got it.

I wrote a grid control that had each cell as an object. It worked very well
except that it got very slow if there were a large number of cells. The
problem was a 100x100 grid was a large number of cells.

I can see that.

Somethings not right there. Dotnet does use more ram so maybe you have
enough for vb6 but not dotnet?

I doubt it. I've got a 2 Ghz machine with 1 GB RAM -- it's a Dell
laptop with XP SP2 on it, and nothing else (besides Firefox
occasionally) is slow.

One thing that is possible is that although I do all my development on
my local harddrive, maybe there are some reasources that are out on our
network...not sure. I dunno. I've seen other people complain about
the speed of .Net, too. Not sure if they were using C# or VB.Net

It's also possible that it takes ages just because you do it
straight after your machine has booted. On my machine it takes a minute to
open anything first up because it is still starting up services etc.

No, that is not the case with mine -- I don't start .Net until I open
up Outlook and check my email then goto lending Tree to see what QFs
are still stuck from the overnight transfers, write those down and call
the Lending Tree help desk and report them. By that time, the machine
has had plenty of time to boot up. I realize that I skipped a couple
of steps in my first griping post, but starting Outlook and Internet
Explorer then closing them down then opening up .Net shouldn't make
that much of a difference from a clean boot.

.



Relevant Pages

  • Re: WHY doesnt C know anything about directories?
    ... is not universal, whereas I think it would be better for the language to include highly common, but not universal, functionality, but supply test functions more or less like this: ... struct is_dirstruct{int notsupported;}; ... because right now one can already choose a cross platform graphics library and work with that. ...
    (comp.lang.c)
  • Re: Wish I was using .net
    ... functionality or having a better import but having this as a default ... the language makes it significantly more difficult. ... reference will by to system.dll. ... Now you add OBJECTS into the listbox. ...
    (microsoft.public.vb.general.discussion)
  • Re: Draft Secure C
    ... completely blind to the problems of the C language. ... A better mapping to functionality commonly available in hardware. ... Better heap functionality. ... That means memory allocation is something that you ...
    (comp.lang.c)
  • Re: identity...... Was: The wisdom of the object mentors
    ... // this is it's implementation/mapping from a hidden domain of {int x int} ... I'd say that the set of all propositions is language defined behavior or ... Boolean object has no place to keep the class identity. ... bool IsBool1() ...
    (comp.object)
  • Re: What kind of Lisp should I learn if I want to start programing with Lisp?
    ... | that just calls the new functionality. ... That's still not a "subset of Common Lisp", ... For a language to be considered a subset, ... CLtL1 Common Lisp. ...
    (comp.lang.lisp)