CC Code Challenge (Week 8) Stumps Engineering Community

We stumped the engineering community with last week’s CC Weekly Code Challenge! We posted a code snippet with an error and challenged you to find the mistake!

Since nobody had the correct answer, we’ve drawn one lucky winner at random from all those who participated.

Congratulations to Marcelo Jimenez of Rio de Janeiro, Brazil for being selected in the CC Weekly Code Challenge – Week 7 drawing! He’ll receive a CC Tag Cloud t-shirt.

The language is Burroughs Corporation “Enhanced” Algol, a rather obscure language these days, though Algol variants were important in their time and are still discussed today in terms of their influence on the structure of subsequent programming languages. The correct answer was: Line 4: incorrect exponent character – it should be “2.99792458@8″

You can see the complete list of weekly winners and code challenges here.

What is the CC Weekly Code Challenge?
Each week, Circuit Cellar’s technical editors purposely insert an error in a snippet of code. It could be a semantic error, a syntax error, a design error, a spelling error, or another bug the editors slip in. You are challenged to find the error.Once the submission deadline passes, Circuit Cellar will randomly select one winner from the group of respondents who submit the correct answer.

Inspired? Want to try this week’s challenge? Get started!

Submission Deadline: The deadline for each week’s challenge is Sunday, 12 PM ESTRefer to the Rules, Terms & Conditions for information about eligibility and prizes.

Alex Ivopol Wins the CC Code Challenge (Week 7)

We have a winner of last week’s CC Weekly Code Challenge, sponsored by IAR Systems! We posted a code snippet with an error and challenged the engineering community to find the mistake!

Congratulations to Alex Ivopol of Wellington, New Zealand for winning the CC Weekly Code Challenge for Week 7! He’ll receive an IAR Kickstart KSK-TMPM061-JL kit.

Alex’s correct answer was randomly selected from the pool of responses that correctly identified an error in the code. Alex answered:

2013_code_challenge_07_answerYou can see the complete list of weekly winners and code challenges here.

What is the CC Weekly Code Challenge?
Each week, Circuit Cellar’s technical editors purposely insert an error in a snippet of code. It could be a semantic error, a syntax error, a design error, a spelling error, or another bug the editors slip in. You are challenged to find the error.Once the submission deadline passes, Circuit Cellar will randomly select one winner from the group of respondents who submit the correct answer.

Inspired? Want to try this week’s challenge? Get started!

Submission Deadline: The deadline for each week’s challenge is Sunday, 12 PM ESTRefer to the Rules, Terms & Conditions for information about eligibility and prizes.

Colm Baston Wins the CC Code Challenge (Week 6)

We have a winner of last week’s CC Weekly Code Challenge, sponsored by IAR Systems! We posted a code snippet with an error and challenged the engineering community to find the mistake!

Congratulations to Colm Baston of Flintshire, UK, for winning the CC Weekly Code Challenge for Week 6! He’ll receive the Elektor 2012 & 2011 Archive DVD.

Colm’s correct answer was randomly selected from the pool of responses that correctly identified an error in the code. Colm answered:

Line 7: (c == *s++) is comparing the values of c and *s rather than assigning: It should be (c = *s++)

You can see the complete list of weekly winners and code challenges here.

What is the CC Weekly Code Challenge?
Each week, Circuit Cellar’s technical editors purposely insert an error in a snippet of code. It could be a semantic error, a syntax error, a design error, a spelling error, or another bug the editors slip in. You are challenged to find the error.Once the submission deadline passes, Circuit Cellar will randomly select one winner from the group of respondents who submit the correct answer.

Inspired? Want to try this week’s challenge? Get started!

Submission Deadline: The deadline for each week’s challenge is Sunday, 12 PM ESTRefer to the Rules, Terms & Conditions for information about eligibility and prizes.

Antonios Chorevas Wins the CC Code Challenge (Week 5)

We have a winner of last week’s CC Weekly Code Challenge, sponsored by IAR Systems! We posted a code snippet with an error and challenged the engineering community to find the mistake!

Congratulations to Antonios Chorevas of Attiki, Greece, for winning the CC Weekly Code Challenge for Week 5! He’ll receive a CC “Tag Cloud” T-shirt and a hardcopy of the CC25 Anniversary Issue.

Antonios’ correct answer was randomly selected from the pool of responses that correctly identified an error in the code. Antonios answered:

Line 04: (x*x) must be replaced by ((x)*(x)) because there is problem with the priority of the operations

 

You can see the complete list of weekly winners and code challenges here.

What is the CC Weekly Code Challenge?
Each week, Circuit Cellar’s technical editors purposely insert an error in a snippet of code. It could be a semantic error, a syntax error, a design error, a spelling error, or another bug the editors slip in. You are challenged to find the error.Once the submission deadline passes, Circuit Cellar will randomly select one winner from the group of respondents who submit the correct answer.

Inspired? Want to try this week’s challenge? Get started!

Submission Deadline: The deadline for each week’s challenge is Sunday, 12 PM ESTRefer to the Rules, Terms & Conditions for information about eligibility and prizes.

Heinz Nickisch Wins the CC Code Challenge (Week 4)

We have a winner of last week’s CC Weekly Code Challenge, sponsored by IAR Systems! We posted a code snippet with an error and challenged the engineering community to find the mistake!

Congratulations to Heinz Nickisch of Bavaria, Germany, for winning the CC Weekly Code Challenge for Week 4! He’ll receive an IAR Kickstart kit.

Heinz’s correct answer was randomly selected from the pool of responses that correctly identified an error in the code. Heinz answered:

Line 37: BEGIN instead of BEING

You can see the complete list of weekly winners and code challenges here.

What is the CC Weekly Code Challenge?
Each week, Circuit Cellar’s technical editors purposely insert an error in a snippet of code. It could be a semantic error, a syntax error, a design error, a spelling error, or another bug the editors slip in. You are challenged to find the error.Once the submission deadline passes, Circuit Cellar will randomly select one winner from the group of respondents who submit the correct answer.

Inspired? Want to try this week’s challenge? Get started!

Submission Deadline: The deadline for each week’s challenge is Sunday, 12 PM ESTRefer to the Rules, Terms & Conditions for information about eligibility and prizes.

Chu Tin Teng Wins the CC Code Challenge (Week 3)

We have a winner of last week’s CC Weekly Code Challenge, sponsored by IAR Systems! We posted a code snippet with an error and challenged the engineering community to find mistake!

Congratulations to Chu Tin Teng of Fremont, CA, for winning the CC Weekly Code Challenge for Week 3! He’ll receive a CC T-Shirt and one-year digital subscription/renewal to Circuit Cellar.

Chu’s correct answer was randomly selected from the pool of responses that correctly identified an error in the code. Chu answered:

Line 7: string comparison should use cmp, instead of <=>. New line should read as “($aa cmp $ba) || ($an <=> $bn)”.

You can see the complete list of weekly winners and code challenges here.

What is the CC Weekly Code Challenge?
Each week, Circuit Cellar’s technical editors purposely insert an error in a snippet of code. It could be a semantic error, a syntax error, a design error, a spelling error, or another bug the editors slip in. You are challenged to find the error.Once the submission deadline passes, Circuit Cellar will randomly select one winner from the group of respondents who submit the correct answer.

Inspired? Want to try this week’s challenge? Get started!

Submission Deadline: The deadline for each week’s challenge is Sunday, 12 PM ESTRefer to the Rules, Terms & Conditions for information about eligibility and prizes.

Chris Austen Wins the CC Code Challenge (Week 2)

It’s Wednesday, which means we’re announcing the winner of last week’s CC Weekly Code Challenge, sponsored by IAR Systems! We posted a code snippet with an error and challenged the engineering community to find mistake!

Congratulations to Chris Austen of South Yorkshire, UK, for winning the CC Weekly Code Challenge for Week 2! He’ll receive a CC Gold issue archive on a USB drive.

Chris’s correct answer was randomly selected from the pool of responses that correctly identified an error in the code. Chris answered:

Line 5: ROT should be SWAP ROT for the given stack effect – though -ROT will work too.

The Code Challenge for Week 2

You can see the complete list of weekly winners and code challenges here.

What is the CC Weekly Code Challenge?
Each week, Circuit Cellar’s technical editors purposely insert an error in a snippet of code. It could be a semantic error, a syntax error, a design error, a spelling error, or another bug the editors slip in. You are challenged to find the error.Once the submission deadline passes, Circuit Cellar will randomly select one winner from the group of respondents who submit the correct answer.

Inspired? Want to try this week’s challenge? Get started!

Submission Deadline: The deadline for each week’s challenge is Sunday, 12 PM ESTRefer to the Rules, Terms & Conditions for information about eligibility and prizes.

CC Weekly Code Challenge Winner

It’s Wednesday, which means we’re announcing the winner of the most recent CC Weekly Code Challenge, sponsored by IAR Systems!

Congratulations to Peter Baston of Flintshire, UK, for winning the CC Weekly Code Challenge for Week 1! He’ll receive an IAR Kickstart: KSK-LPC4088-JL.

Peter’s correct answer was randomly selected from the pool of responses that correctly identified an error in the code. Peter answered Line 9: There should not be a “*” before argv[i].

You can see the complete list of weekly winners and code challenges here.

 

What is the CC Weekly Code Challenge?
Each week, Circuit Cellar’s technical editors purposely insert an error in a snippet of code. It could be a semantic error, a syntax error, a design error, a spelling error, or another bug the editors slip in. You are challenged to find the error.Once the submission deadline passes, Circuit Cellar will randomly select one winner from the group of respondents who submit the correct answer.

Inspired? Want to try this week’s challenge? Get started!

Submission Deadline: The deadline for each week’s challenge is Sunday, 12 PM ESTRefer to the Rules, Terms & Conditions for information about eligibility and prizes.