Re: Dictionary possibilities [Re: Interesting... AppleScript X??]
Re: Dictionary possibilities [Re: Interesting... AppleScript X??]
- Subject: Re: Dictionary possibilities [Re: Interesting... AppleScript X??]
- From: has <email@hidden>
- Date: Sat, 28 Sep 2002 11:41:55 +0100
Timothy Bates wrote:
>
> (As a mental exercise, here's how this might work for an AS user. The user
>
> might begin a line by typing "make". The editor would then pop up a list at
>
> side of the screen, showing the names of all possible objects that can be
>
> made in the current context.
>
>
This is exactly how Cal Simone's Script Editor used to work (well, still
>
does if you are still using it). So you learn more about the magic Cal
>
without knowing.
The funny thing about "new" ideas is that they often turn out to be old
ideas previously overlooked as "ahead of their time". The verb-noun
division actually starts to make sense once put into a context like this. I
wonder what they were thinking not to use this.
As for LabVIEW, perhaps it's an indication that the best way to get a new
paradigm in will be through a back door first. Pick a group of people who
have no preconceptions about what a programming environment should be, and
push it to them. Then wait to see how long before the 'Real Programmers'
all scornfully start looking down their noses at it. For, as we all know
now, the Macintosh was also just some toy that'd never catch on...;p
--
Michael Sullivan wrote:
>
No, it would not. Compiled scripts are already compiled to a bytecode
>
format. The key is not "plaintext", but a published spec.
Said it far better than I.
>
But a code program like this, I think there are potentially major
>
advantages from storing code in a more complex data format, *IF* it
>
could be made robust enough. Somehow I doubt this would work in
>
practice.
I'm quite sure it could. And what's stored to disk or imported/exported
doesn't need to be in the same form as the internal model, though for
day-to-day use it's probably to be preferred. Binary format for day-to-day
use (nothing new in this), with import/export to XML or some other plain
text format for archiving and exchange.
>
One of the things I love about lisp family languages (even though many
>
folks hate the parentheses) is that the plain-text source code *is* the
>
parse tree. The parens define the parse tree, so with an editor that
>
indents to paren levels, you can see the parse tree visually looking at
>
nothing but the text file.
Neat. First one to write a LISP editor/interpreter in AppleScript wins the
prize. ;)
has
--
http://www.barple.pwp.blueyonder.co.uk -- The Little Page of AppleScripts
_______________________________________________
applescript-users mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/applescript-users
Do not post admin requests to the list. They will be ignored.