View unanswered posts | View active topics It is currently Fri Nov 24, 2017 12:49 pm






Reply to topic  [ 6 posts ] 
Please decouple the RobotC editor and compiler 
Author Message
Rookie

Joined: Sat Sep 27, 2014 5:14 pm
Posts: 7
Post Please decouple the RobotC editor and compiler
(N.B.: I'm not sure if this is in the right section. I'm used to using real bug trackers, which tend to put feature requests alongside actual bugs, but feel free to move if it's not in the right spot.)

Some of us can't stand using particular editors for various reasons. For example, I'm a religious user of Emacs. I'm used to typing C-n (Ctrl-N) to go to the next line. Sometimes I accidentally type this into RobotC, and I get a new file. Not the desired behavior. I could list countless other things that I wish were in the RobotC editor. The solution is not to put all these things in the editor, of course (unless you are fine with embedding a Lisp interpreter into RobotC and replicating all of the existing interfaces of Emacs, including buffers, windows, frames, etc.). That would take decades, as it has for Emacs, to evolve.

No, the solution is to allow the use of another editor. The ties between the RobotC compiler and the RobotC editor are arbitrary and restrictive. Any real programming language allows you to use the compiler independently of the editing environment. C++ has the GNU Compiler Collection's g++ or Clang+LLVM. C has gcc and/or Clang+LLVM. Take your pick. Even Microsoft's Visual Studio tools allow you to run compilers on the commandline. So why doesn't RobotC?

It's 2014. Compilers have been written to be run standalone for 52 years now. IDEs have been around for 29, pretty much always shipping with independent compilers.

Please decouple the RobotC compiler from the RobotC IDE.

_________________
---

Alex Jordan (AJ)
FTC 5619
SAAS Robotics


Wed Oct 08, 2014 11:42 pm
Profile WWW
Novice

Joined: Tue Dec 11, 2012 9:19 pm
Posts: 58
Post Re: Please decouple the RobotC editor and compiler
+1.

Although I use vi.

http://en.wikipedia.org/wiki/Editor_war


Thu Oct 09, 2014 2:05 am
Profile
Novice

Joined: Tue Dec 11, 2012 9:19 pm
Posts: 58
Post Re: Please decouple the RobotC editor and compiler
And I'm introducing my team to github along with
git for windows which ships with a bash shell along
with vi as the default editor for commit comments.

An ideal workflow would be

vi foo.c
make
make deploy

and if you really don't want to deal with real projects and makefiles

vi foo.c
robotc foo.c
deploy foo


Thu Oct 09, 2014 2:14 am
Profile
Rookie

Joined: Sat Sep 27, 2014 5:14 pm
Posts: 7
Post Re: Please decouple the RobotC editor and compiler
skatefriday wrote:


I am aware of what a holy war is, haha! In the interest of not making the RobotC devs wade through a series of increasingly religious arguments, and thus ignoring this request entirely, I will resist the urge to comment on your exceedingly poor choice of editor.

Also, I'm glad I'm not the only one! I was beginning to wonder...

_________________
---

Alex Jordan (AJ)
FTC 5619
SAAS Robotics


Fri Oct 10, 2014 1:46 am
Profile WWW
Rookie

Joined: Sat Sep 27, 2014 5:14 pm
Posts: 7
Post Re: Please decouple the RobotC editor and compiler
skatefriday wrote:
And I'm introducing my team to github along with
git for windows which ships with a bash shell along
with vi as the default editor for commit comments.


Just to point out: the reason that msysgit ships vi is because Git defaults to it. That's the reason that it's there; not because of the preference of the msysgit maintainer. If you use GitHub for Windows' Git Shell (possibly only with PowerShell; I'm not sure), you'll notice it uses the more user-friendly and clearly far superior notepad.exe.

skatefriday wrote:
An ideal workflow would be

vi foo.c
make
make deploy

and if you really don't want to deal with real projects and makefiles

vi foo.c
robotc foo.c
deploy foo


*a single tear rolls down the side of my face as I weep for joy at the glorious vision in my mind*

_________________
---

Alex Jordan (AJ)
FTC 5619
SAAS Robotics


Fri Oct 10, 2014 1:50 am
Profile WWW
Novice

Joined: Tue Dec 11, 2012 9:19 pm
Posts: 58
Post Re: Please decouple the RobotC editor and compiler
strugee wrote:
skatefriday wrote:
And I'm introducing my team to github along with
git for windows which ships with a bash shell along
with vi as the default editor for commit comments.


Just to point out: the reason that msysgit ships vi is because Git defaults to it. That's the reason that it's there; not because of the preference of the msysgit maintainer. If you use GitHub for Windows' Git Shell (possibly only with PowerShell; I'm not sure), you'll notice it uses the more user-friendly and clearly far superior notepad.exe.


I wasn't making a commentary on vi. One can wikipedia:Editor_Wars for that.

And I must presume that the notepad.exe comment is sarcasm. My sarcasm antenna is
in the shop for repairs but I think I can still recognize that one.


Fri Oct 10, 2014 5:00 pm
Profile
Display posts from previous:  Sort by  
Reply to topic   [ 6 posts ] 

Who is online

Users browsing this forum: No registered users and 2 guests


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot post attachments in this forum

Search for:
Jump to:  
cron



Powered by phpBB © 2000, 2002, 2005, 2007 phpBB Group.
Designed by ST Software for PTF.