Explanation of satellite data from a programmer’s perspective
I have started reading Part 2 of Introduction to Algorithms and in the section The structure of the data the author/authors says in the context of sorting a sequence of numbers:
Why are errors named as “Exception” but not as “Error” in programming languages?
I’ve been thinking about that for quite a while actually. I am not a native English speaker myself but still, I have years of programming experience and I always asked myself this. Why is it named as Exception but not Error since they are errors?
Term for 24-bits
Is there a term for a 24-bit (3-byte) integer?
What do you call “X <= $foo <= Y" comparison?
While writing a Perl statement like if ( $foo >= X && $foo <= Y ) yet again, I wondered why many programming languages do not support the more comfortable form if ( X <= $foo <= Y ) and what this is called. I came up with “3-legged comparison” but no results when searching for it. By the way there is also the “element-of-set” form if ( $foo in X..Y ) which I only consider more readable when provided via a short keyword.
Is there a name for this use of the State design pattern?
I’m looking to see if there is a particular name for this style of programming a certain kind of behavior into a program.
Name for this antipattern? Fields as local variables [closed]
Closed 10 years ago.
ISTQB terminology question (Defect)
According to ISTQB (and few more sources + wiki ), a defect/bug is the actual cause of error in software, e.g. incorrect statement, logical or semantic error. The actual definion is: a flaw in the system or component that could lead to the failure.
But what about specification bugs? I cannot relate to it. Specification bugs are quite common but if the programmer implements software according to spec with a bug, it is not his fault (IMHO). But then the definion could not apply and I am sure it must have been addressed somehow. Could you help me to understand this?
What Does It Usually Mean for a Feature to be “Supported”?
I’m currently working some testing for a particular area of an application. I had to write some automated tests for a particular feature but due to the circumstances, this was not easy to do. When I asked one of the other testers about it, he mentioned that the same features exist in a sister application our company produces but isn’t documented anywhere (end-user documentation or otherwise). He also said that the feature doesn’t typically get tested at all in the sister application and isn’t usually tested in the application I work on. Apparently this feature isn’t heavily used but removing it would require a fair bit of work so the benefit-cost ratio doesn’t work out.
What Does It Usually Mean for a Feature to be “Supported”?
I’m currently working some testing for a particular area of an application. I had to write some automated tests for a particular feature but due to the circumstances, this was not easy to do. When I asked one of the other testers about it, he mentioned that the same features exist in a sister application our company produces but isn’t documented anywhere (end-user documentation or otherwise). He also said that the feature doesn’t typically get tested at all in the sister application and isn’t usually tested in the application I work on. Apparently this feature isn’t heavily used but removing it would require a fair bit of work so the benefit-cost ratio doesn’t work out.
What’s the equivalent name of “procedure” in OOP?
In several of my programming courses in the University, my teachers always told me the following: