On Sunday, July 13, 2003, at 03:29 AM, David Ledger wrote:
The sooner 'Project Builder' can create perl or shell projects
directly the better.
What sort of projects? A simple .pl file doesn't really need a
project - it's just a single file. You can use PB to edit it,
although BBEdit is
Le samedi, 12 juil 2003, à 17:25 Europe/Paris, Steven Bach a écrit :
But I fully agree with Chris that it is purely a matter of opinion
whether Perl is hard compared to AS, and I would add that programming
backgrounds, learning styles and other factors are likely to come into
play.
May I add
I agree that the semantic distinction is very tenuous. However, I
disclaim any ownership or responsibility for it - it's not *my*
distinction. It's a marketing distinction, and personally I find
it not only a patently false distinction but also an intentionally
misleading one - AppleScript
On Sunday, July 13, 2003, at 03:29 AM, David Ledger wrote:
The sooner 'Project Builder' can create perl or shell projects directly
the better.
What sort of projects? A simple .pl file doesn't really need a project -
it's just a single file. You can use PB to edit it, although BBEdit is
On Saturday, July 12, 2003, at 07:30 am, Jeff Lowrey wrote:
AppleScript, on the whole, has a shorter learning time FOR A
PROGRAMMER to be productive than Perl does.
Given that any language will try to provide the functionality that the
user culture currently requires of it, all languages have
Well, that's flat-out ridiculous.
Perl is HARD compared to Applescript.
That is a matter of opinion.
Actually, it's NOT a matter of opinion. Many people have differing
opinions, but that's not the same thing.
It's a matter of marketing, flat out.
...
However, AppleScript is a scripting
At 10:25 AM -0500 7/12/03, Steven Bach wrote:
Well, that's flat-out ridiculous.
Perl is HARD compared to Applescript.
That is a matter of opinion.
Actually, it's NOT a matter of opinion. Many people have
differing opinions, but that's not the same thing.
It's a matter of marketing, flat
In article [EMAIL PROTECTED],
[EMAIL PROTECTED] (Chip Howland) wrote:
At 1:10 AM +0900 7/11/03, Robin wrote:
But if I have to have a double clickable perl script I prefer using
the '.command' technique because I really believe Apple should just
go ahead and use Perl as the scripting
At 10:29 AM -0700 7/11/03, Chris Nandor wrote:
and here's a Perl tutorial:
[snip way too many lines of tutorial, apparently intended to make perl look
a lot harder than it is]
Here is what, perhaps, you meant:
Open BBEdit
Type
print Hello, world.
Run the script
Yes, that's one way to run a
On Friday, July 11, 2003 14:14 -0500 Chip Howland [EMAIL PROTECTED]
wrote:
I think you might be a special case. Not everyone has written Mac::Glue
or maintained MacPerl. If you are claiming that you can do everything
with Perl and Mac::Glue that you can with Applescript, then I won't
dispute
In article [EMAIL PROTECTED],
[EMAIL PROTECTED] (Chip Howland) wrote:
At 10:29 AM -0700 7/11/03, Chris Nandor wrote:
and here's a Perl tutorial:
[snip way too many lines of tutorial, apparently intended to make perl look
a lot harder than it is]
Here is what, perhaps, you meant:
In article [EMAIL PROTECTED],
[EMAIL PROTECTED] (David Cantrell) wrote:
It matters not that he wrote Mac::Glue. He's published it, so I can use it
too. And I have just as much difficulty with using Mac::Glue as I do with
using Applescript. That difficulty is solely because Applescript
At 10:29 AM -0700 7/11/03, Chris Nandor wrote:
In article [EMAIL PROTECTED],
[EMAIL PROTECTED] (Chip Howland) wrote:
At 1:10 AM +0900 7/11/03, Robin wrote:
But if I have to have a double clickable perl script I prefer using
the '.command' technique because I really believe Apple should just
On Sunday, May 11, 2003, at 7:04 AM, John Delacour wrote:
Whatever you can do with DropScript you can do more conveniently with
Perl in an AppleScript droplet that _does_ know where it is.
On Thursday, July 10, 2003, at 03:37 am, Wilfredo Sánchez wrote:
The assumption that your working
At 1:10 AM +0900 7/11/03, Robin wrote:
But if I have to have a double clickable perl script I prefer using
the '.command' technique because I really believe Apple should just
go ahead and use Perl as the scripting language and put AppleScript
to bed along with OS9
Well, that's flat-out
On Sunday, May 11, 2003, at 7:04 AM, John Delacour wrote:
Whatever you can do with DropScript you can do more conveniently with
Perl in an AppleScript droplet that _does_ know where it is.
The assumption that your working directory is where your script lives
is broken.
You script's path is
16 matches
Mail list logo
