Go to Post the FIRST season is never over . . it just pauses a while so you can get some sleep. - Stuart [more]
Home
Go Back   Chief Delphi > Competition > OCCRA > OCCRA Programming
CD-Media   CD-Spy  
portal register members calendar search Today's Posts Mark Forums Read FAQ rules

 
 
 
Thread Tools Rating: Thread Rating: 2 votes, 5.00 average. Display Modes
Prev Previous Post   Next Post Next
  #4   Spotlight this post!  
Unread 03-10-2011, 21:02
apalrd's Avatar
apalrd apalrd is offline
More Torque!
AKA: Andrew Palardy (Most people call me Palardy)
VRC #3333
Team Role: College Student
 
Join Date: Mar 2009
Rookie Year: 2009
Location: Auburn Hills, MI
Posts: 1,347
apalrd has a reputation beyond reputeapalrd has a reputation beyond reputeapalrd has a reputation beyond reputeapalrd has a reputation beyond reputeapalrd has a reputation beyond reputeapalrd has a reputation beyond reputeapalrd has a reputation beyond reputeapalrd has a reputation beyond reputeapalrd has a reputation beyond reputeapalrd has a reputation beyond reputeapalrd has a reputation beyond repute
Re: [OCCRA]: EasyC Text Editor?

My biggest issue with the easyC graphical environment is that it isn't a good graphical environment.

Having worked with embedded C (for PIC, HCS12 and MCP55xx 16 and 32 bit controllers with various degrees of RTOS included), embedded Simulink (run through Embedded Coder and compiled as C), and RT LabVIEW (for FRC), I personally prefer the Simulink/LV graphical implementation as it represents what it happening much better than easyC does.

With easyC, I can SEE the C code right there, and know exactly what I want to type (full of tricks with typedef enums, defines, bitwise logic and such) and type it really fast, with a bunch of logic and math operations on one line. With easyC, I can SEE the code, but I can't type it, and have to search through the library to find the block I want.

The best embedded environment I ever worked with was the HCS12 embedded ECU. The development library had been extended (internally) to include a basic RTOS, with interrupt-based CAN message handling and pre-emptive scheduling. The best part was, that since it was developed internally, I could pull down the source of the RTOS from SVN and see exactly how the library did something if I questioned how it did something, or if I had a big issue, I could just change it in the library (and if it was REALLY big, I could email the guy who wrote it and ask him about it). The easyC library is very black-box to me, and I don't like the inability to change things. There are many things to me which would be much easier for me to implement in the hardware interrupts (such as encoder speed handling), but I can't because I can't modify the library code.

That said, RobotC isn't a lot better on the black-box issue. I like the environment more, though.
__________________
Kettering University - Computer Engineering
Kettering Motorsports
Williams International - Commercial Engines - Controls and Accessories
FRC 33 - The Killer Bees - 2009-2012 Student, 2013-2014 Advisor
VEX IQ 3333 - The Bumble Bees - 2014+ Mentor

"Sometimes, the elegant implementation is a function. Not a method. Not a class. Not a framework. Just a function." ~ John Carmack
Reply With Quote
 


Thread Tools
Display Modes Rate This Thread
Rate This Thread:

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Forum Jump


All times are GMT -5. The time now is 02:42.

The Chief Delphi Forums are sponsored by Innovation First International, Inc.


Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2017, Jelsoft Enterprises Ltd.
Copyright © Chief Delphi