71–80 of 89 posts
Earlier quoted context omitted.
No but everyone should jump away from SourceForge after the shady crap they pulled. Gitlab is also a thing.
SourceForge has now long been under a different ownership then when the shaddy crap happened. Since ownership changed there has been no shaddy behavior.
Linux fans sometimes reminds me of vegans : they always have to transpose what they had before their new "religion". So we have zucchini noodles and GAMBAS an "almost basic" for Linux. Usually the original is much better (can't say for GAMBAS, but zucchini noodles certainly aren't noodles !). To me it means you're not comfortable with your new environment, you came here for ideological reasons, not because the new on…
Bad example. Noodles ARE vegan.
It seems that Microsoft was aware of the poor quality of its language, as VB .Net is not backward compatible with older versions of Visual Basic.
I dislike the bad level of common Visual Basic programmers, often due to bad pratices imposed by the bugs and strangeness of this language.
Pity he couldn't resist taknng a swipe at vb and vb programmers in his introduction. Also he's inaccurate wrt to his comments about why Microsoft didn't make a vb7.
Earlier quoted context omitted.
Yes. It basically outputs the executable binary for the target you choose when compiling your Haxe code. It means you write Haxe source and the 'compiler' (transpiler, actually) generates code for the choosen target. It will then compile the generated code using the target compiler installed in your system, if necessary (when you target C++, for example).
So how we debug the code? I mean other than various form of logging/dump.
Earlier quoted context omitted.
Or, worse, and common in classic VB, ON ERROR RESUME NEXT. Which just skips the line that errored.
It sets Err. Which is essentially how SH, C and Go work too. (With the obvious exceptions of longjmp and panic/defer, global vs local var, and Go forcing to assign the error.) On Error Resume Next isn't great, but calling it much worse than On Error Goto, or much worse than other languages, is a stretch. My point is only that people complain about it in VB disproportionally often compared to other languages. (Does th…
Earlier quoted context omitted.
Don't you think that "ideological reasons" can be quite a good reason to do things? Besides, following ideological reasons only means to value certain (other) aspects higher for evaluating the question how good something is. Usually the term ideological implies (in my book) that a person is considering the greater good, and willing to take a step back in own convenience. That sounds like a nice person to me. Maybe yo…
Ideology is all fine and well until you start to deviate too much from reality. Then you hit a wall. Example : there are cases of babies dying because their parents refused to give them animal milk. Be pragmatic : you don't want to hurt animals, OK, but why not raising a couple chicken to get some eggs ? Fwiw, my servers are Linux, but my desktop is Windows (it's not for lack of trying Linux as a desktop).
Earlier quoted context omitted.
It sets Err. Which is essentially how SH, C and Go work too. (With the obvious exceptions of longjmp and panic/defer, global vs local var, and Go forcing to assign the error.) On Error Resume Next isn't great, but calling it much worse than On Error Goto, or much worse than other languages, is a stretch. My point is only that people complain about it in VB disproportionally often compared to other languages. (Does th…
I don’t think I’ve ever seen any vb code which actually checks that, though,or dry little, certainly. In C and Go you get something returned, which is a hint that you should maybe do something with it. In VB a magic global variable is set, and then generally ignored.
Usually much cleaner than jumping to somewhere else, but that had its uses too.
Earlier quoted context omitted.
I don’t think I’ve ever seen any vb code which actually checks that, though,or dry little, certainly. In C and Go you get something returned, which is a hint that you should maybe do something with it. In VB a magic global variable is set, and then generally ignored.
That's how I've done it. Enable it before the line(s) in question, then check err.number, and add "On Error Goto 0" after that so you get the default handler again. Usually much cleaner than jumping to somewhere else, but that had its uses too.