News for hackers. Stuff that matters.
Re:A startup's "Why we use Lisp" story by philwelch on Thursday January 14, 2010 @01:39PM (#1053241)
"You haven't seen XCode, Delphi or MS Visual Studio, where, for example, you can jump to the definition of a symbol with "one click""

That's an old feature. It used to be called "ctags" and even console-based text editors support it.

"Finally getting to the point and you say "and all that"? Btw, "all that" includes unification of code and data - something no other language provides, let's say, idiomatically. This is an amazing feature, and in fact Lisp macros are Lisp macros thanks to just that - unification of code and data and symbolic nature of the language."

Lisp's problem seems to be that, until you know how to use macros and code/data unification, you can't be easily convinced of their merits. It takes a considerable commitment to learn Lisp before you can reach that level, though.

Re:A startup's "Why we use Lisp" story by lg on Thursday January 14, 2010 @04:08PM (#1053599)
Yeah, Slime does this and without ctags, I believe most lisps keep track of the location of definitions in source.

But what's a definition? Slime does this for defun/defvar etc, but not for things defined with, say, hunchentoot's define-easy-handler. Can you tell your IDE to take me to that location in a single keystroke? Maybe Slime supports adding definition types, I have no idea. Or maybe it throws up its hands because of the potential naming conflicts.

All this makes you wonder whether Lisp is too powerful for any IDE to keep up.

Re:A startup's "Why we use Lisp" story by lispm on Thursday January 14, 2010 @05:00PM (#1053687)
LispWorks does that. You can add your own ways to record source locations of your definition forms.

http://www.lispworks.com/documentation/lw60/LW/html/lw-60.ht...

Re:A startup's "Why we use Lisp" story by gchpaco on Thursday January 14, 2010 @04:55PM (#1053682)
You can do that, it's not terribly difficult, just picky.
Re:A startup's "Why we use Lisp" story by bitwize on Thursday January 14, 2010 @02:18PM (#1053344)
That's an old feature. It used to be called "ctags" and even console-based text editors support it.

Have you ever used IntelliSense?

Re:A startup's "Why we use Lisp" story by philwelch on Thursday January 14, 2010 @03:40PM (#1053541)
Yes, and it's a very useful feature I haven't found an equivalent to yet, That's not quite what we were talking about though--it's far beyond jumping to the definition of a symbol with a click.

IntelliSense doesn't always work, either, at least when I used Visual Studio a lot.

Re:A startup's "Why we use Lisp" story by city41 on Thursday January 14, 2010 @05:06PM (#1053699)
Which version of Visual Studio? Intellisense in VS, at least as of 2008, is pretty much rock solid. I can't think of a time when it has failed on me.
Re:A startup's "Why we use Lisp" story by philwelch on Thursday January 14, 2010 @05:47PM (#1053767)
In '03 and '05 Intellisense would intermittently quit, but start working again after a build.
Re:A startup's "Why we use Lisp" story by jjwiseman on Thursday January 14, 2010 @07:38PM (#1053954)
I'm often saddened that because CLOS doesn't use a message-passing paradigm (and because Lisp's syntax is prefix?), doing traditional Intellisense-style method listing and completion is nearly impossible.
Re:A startup's "Why we use Lisp" story by ytinas on Friday January 15, 2010 @07:19AM (#1054730)
I wouldn't be impossible, it just wouldn't work the way a message passing language does. If you ask me the trade off wouldn't be remotely worth it.

You could e.g. have a system where write some type name (or variable with a declared type), hit a key and get a list of all the generic methods that apply.

Re:A startup's "Why we use Lisp" story by Zak on Friday January 15, 2010 @11:59AM (#1055238)
It would be a small matter of programming to add a function to Slime that, upon typing a symbol presents a list of every function that's reasonably likely to apply to it. I think the reason I haven't seen it is that it represents a very noun-oriented way of thinking about programming. Lispers are less likely to program that way than say Java programmers, where the language enforces the style.
Re:A startup's "Why we use Lisp" story by makmanalp on Thursday January 14, 2010 @02:23PM (#1053357)
ctags are a pain to set up and not nearly comparable to what exists today.
Re:A startup's "Why we use Lisp" story by lispm on Thursday January 14, 2010 @02:25PM (#1053362)
jumping to definitions is nothing that is new. My Lisp Machine can edit/modify all source code of the entire operating system while it is running. It knows the location of every single definition.
Re:A startup's "Why we use Lisp" story by vdm on Friday January 15, 2010 @07:54AM (#1054769)
Screencasts?