The Weird and The Wonderful

CPallini wrote:

The following was mine

...
double cosa = cos( alfa );
double sina = sin( alfa );
for (i = 0; i < POINTS; i++)
{
  double dx = x[i] - x;
  double dy = y[i] - y;
  x[i] = x + dx * cosa - dy * sina;
  y[i] = y + dx * sina + dy * cosa;
}

martin_hughes wrote:

Just got off the blower to a colleague who is having a very bad day

martin_hughes wrote:

C++/Java/C# guys who claim to 10-15 years working with their chosen languages

while (true)   // loop 1 time, exit at bottom
{
    if (set (ifrFragment))
    {
        result = true;
        ifrTerm = ifrFragment;
        break;
    }
    if (errorCode)
        break;

    if (keyword (TokenSubtype::Not) && term (ifrFragment))
    {
        result = true;
        ifrTerm = TokenSubtype::Not.asString() + " " + ifrFragment;
        break;
    }
    if (errorCode)
        break;
  // more lines snipped
   break;
}

Robert Surtees wrote:

We used to do it to piss off the "never use goto" zealots years ago when forbidden to use 'goto xit' for handling error conditions.

 if (keyword (TokenSubtype::Group))
 {
     if (!group_label (groupName))
     {
         errorMessage = myName + ": Missing GROUP label\n" + errorMessage;
         errorCode = DL_ERROR;
         goto exit_;
     }

     if (!separator (TokenSubtype::Colon))
     {
         errorMessage = myName + ": Missing colon following GROUP label";
         errorCode = DL_ERROR;
         goto exit_;
     }
// etc...

chmod2222 wrote:

I use goto only to break out of >1 nested loops... Don't see the need for it anywhere else...