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.

Design West Update: Compilers Unveiled

IAR Systems announced Tuesday at Design West in San Jose, CA, that GainSpan selected IAR Embedded Workbench as its primary development tool chain for MCU drivers and next-generation chip. “By standardizing on IAR Systems’ embedded software development tool chain, GainSpan will more easily support a wide range of MCUs to communicate with their modules,” IAR publicized a in a release.

It’s an important aspect of a larger plan, IAR’s ARM Strategic Accounts Manager Mike Skrtic said. IAR has overall tool chain standardization goals aimed at giving designers’ more flexibility when choosing MCUs for product development.

Remember: IAR Systems is teamed with Renesas for the RL78 Green Energy Challenge, which is administered by Circuit Cellar and Elektor. Designers are challenged to transform how the world experiences energy efficiency by developing a unique, low-power application using the RL78 MCU and IAR toolchain.

In other compiler-related news, Microchip Technology announced Monday at Design West its new MPLAB XC C compiler line, which supports its approximately 900 microcontrollers. Microchip’s Joe Drzewiecki said the compilers reduce code size by about 35% and improve code execution speed by about 30%. But you can judge for yourself because Microchip offers 8-, 16-, and 32-bit free editions of MPLAB XC compilers. According to Microchip reps, they are” fully functional and have no license restrictions for commercial use.”

So, if you give MPLAB XC a try, let us know what you think!