Discussion on:
View:
Show:
I thought Microsoft produced a new design guideline that states you no longer have to use Hungarian prefixes and use prefixes for fields.
would have completely ignored it if I had. Apart from the crap about using labels and gotos to exit from one place in a function/sub I didn't see anything objectionable in there. Indeed I use all of the other techniques. In any language, not just VB.
I've been programming like that since college.
except in the middle ages of programming, it was:
i = int
c = char
and such...etc etc.
except in the middle ages of programming, it was:
i = int
c = char
and such...etc etc.
Nearly anyway
i = int // an integer called i
c = char // a letter variable called c
Comments add so much to your code don't they
LOL
Based on some of the fresh faced graduates I've had to mentor, it would seem so anyway.
i = int // an integer called i
c = char // a letter variable called c
Comments add so much to your code don't they
LOL
Based on some of the fresh faced graduates I've had to mentor, it would seem so anyway.
was in one of the books we used...btw, it wasn't a Microsoft Press book either.
I'll look it up...I have all my old CS books from back in the stone ages.
I'll look it up...I have all my old CS books from back in the stone ages.
we used line numbers, variable names were limited to seven characters and it was clever to do a program with GOTOs in it.
VB.NET's MS-suggested naming conventions explicitly specify ditching Hungarian notation altogether. I agree! Dammit! Check recent .NET Framework docs if you don't believe me (Naming Conventions - Variables section).
after all, Visual coding with a drag and drop design system is what creates the worst possible code.
so, vb being 95% drag and drop coding, it can never have better code.
so, vb being 95% drag and drop coding, it can never have better code.
in Drag and drop, but they didn't do much and that badly. I average about 95% in written code. Course if you looked at what VB calls an executable, even discounting all the ms dlls and 3rd party ocxs. The %age is probably correct.
Mind you if you ripped out all the excess gargbage that the p1ss poor excuse for a compiler puts in you could halve that without breaking into a sweat.
Mind you if you ripped out all the excess gargbage that the p1ss poor excuse for a compiler puts in you could halve that without breaking into a sweat.
drag and drop is good for adding unneeded code, and interface design.
yet, you could set up a basic interface that every app will have then just open that and tweak the settings.
you might even get a 98% coding avarage then.
I personally like to use copy for interface objects, since then I can remove code from each interface object that isn't needed by an application.
the drag and drop is much faster for interface design than manually coding each button, menu, toolbar etc.
yet, you could set up a basic interface that every app will have then just open that and tweak the settings.
you might even get a 98% coding avarage then.
I personally like to use copy for interface objects, since then I can remove code from each interface object that isn't needed by an application.
the drag and drop is much faster for interface design than manually coding each button, menu, toolbar etc.
- Keyboard Shortcuts:
- Prev
- Next
- Toggle
