Apple Dylan PPC Bug
Ashley Branchfeather
Using the PPC version of Apple Dylan, you can't change the names of any
source folders or modules. You can in the 68k version...
--
Ashley Branchfeather
Ashley Branchfeather
In article <AshleyB-2408...@news.halcyon.com>,
Ash...@halcyon.com (Ashley Branchfeather) wrote:
>Using the PPC version of Apple Dylan, you can't change the names of any
>source folders or modules. You can in the 68k version...
You can't delete items (source records, folders etc.) either.
--
Ashley Branchfeather
Ashley Branchfeather
[Gabor Greif <ga...@datawatch.osn.de> asked me to post this]
In article <AshleyB-2508...@news.halcyon.com>,
Ash...@halcyon.com (Ashley Branchfeather) wrote:
>>Using the PPC version of Apple Dylan, you can't change the names of any
>>source folders or modules. You can in the 68k version...
>
>You can't delete items (source records, folders etc.) either.
Well, that's quite annoying! How could the folks porting the TR1 to PPC
overlook that? You just have to follow the steps of "Apple Dylan
Quickstart" Chapter 4, "Creating Your Own Projects" to detect this
shortcoming.
At least you can export your project, rename the files to match the desired
names for source folders and modules, and then reimport everything into a
brand new project.
Did I now overlook an obvious solution?
Are there more elegant workarounds?
Patches from Digitool or Apple?
Well, this is my first night with Apple Dylan ... :-)
Gabor
Tim Pritlove
>any
>>>source folders or modules. You can in the 68k version...
>>
>>You can't delete items (source records, folders etc.) either.
>
>Well, that's quite annoying! How could the folks porting the TR1 to
PPC
>overlook that?
Well, Digitool did nothing but _porting_ the code base to the PPC.
This means, they just re-compiled with the new MCL compiler, I guess.
Problems like these might lay deep in good old MacOS (you, the OS that
still doesn't run native on our computers).
But AppleDylan PPC is fast. So use it for entering new code and
compile and test it. Switch over to the 68K version to change folder
names and erase unused stuff. It works.
Don't forget: Digitool's Emulator control panel allows to switch off
the new caching mechanism in the 68k emulator code.
Tim
Robert D. Skeels
in article <AE5358C...@10.1.1.151>
Tim Pritlove <t...@artcom.de> writes:
>Well, Digitool did nothing but _porting_ the code base to the PPC.
I understand what you meant, but I have to say that a good port would
require the port to have the exact functionality of the 68K TR1--bugs and
all. I would much rather have had the PPC version with just the original
problems instead of the original problems plus the new ones.
Since defined name space is so important in Dylan, the inability to name
anything in the PPC release makes it difficult to just...
>Switch over to the 68K version to change folder names and erase unused
stuff.
For any project beyond one module, I'm better off just staying in the 68K
version. That way the environment doesn't claim this and that are not
defined.
>Don't forget: Digitool's Emulator control panel allows to
>switch off the new caching mechanism in the 68k emulator code.
To Digitool's credit Emulator has made my work in Dylan tolerable for the
past six months. If I had been patient and watched this group for first
impressions of the PPC release (instead of checking every day to buy it), I
could have saved fifty bucks. So in the long run I have no one to blame but
myself.
Just rambling now...
I was hoping that the PPC release would allow us to start writing some
useful code in a reasonable amount of time. I sincerely believe that the
much higher than expected sales of TR1, the ongoing Dylan work on other
platforms, and some cool stuff written in Apple Dylan would get Apple to
change its mind on the project. One or two popular free-shareware Internet
aps written in Dylan might be what it takes (beyond my programing scope).
I don't buy the TR1 sales were high because of the price argument that I've
seen on this group. I could get Code Warrior for $100 plus what I've spent
on Dylan to date. I really think that most people have invested in Apple
Dylan because they are interested in the language. At least that's why I
have.
IBM UNLEASHES THE 225 MHz PowerPC 604e--WORLD'S FASTEST DESKTOP CPU
---------------------------| * * * * * * * * * * * * *
This message created and | Learn more about the PowerPC Revolution
sent via the Cyberdog Mail | http://www.chips.ibm.com/products/ppc
System from Apple Computer | /L2allabout.html
---------------------------|
http://home.earthlink.net/~athene
This mail came from a PowerPC based computer
Robert D. Skeels ath...@earthlink.net
Los Angeles, CA (213) 665-0845
freelance illustration & design
Senior UCLA-Classical Civilization
eti kai nun Hellas phileo
Andrew Shalit
In article <AE5ACA9...@206.250.113.130>,
"Robert D. Skeels" <ath...@earthlink.net> wrote:
>in article <AE5358C...@10.1.1.151>
>Tim Pritlove <t...@artcom.de> writes:
>
>>Well, Digitool did nothing but _porting_ the code base to the PPC.
>
>I understand what you meant, but I have to say that a good port would
>require the port to have the exact functionality of the 68K TR1--bugs and
>all. I would much rather have had the PPC version with just the original
>problems instead of the original problems plus the new ones.
The port was not trivial. The people at Digitool worked their buns off to
make it as good as possible. It seems like they introduced a serious bug.
I think that's a real shame, but it's not because they were needlessly
massaging the code. It's just that there really are differences between
MCL 3.0 and MCL 4.0.
I'd recomend reporting this bug directly to Digitool, or to one of the
hackers there. (You could try bi...@digitool.com and s...@digitool.com.)
It wouldn't surprise me if they came up with a patch in their spare
time.
As far as posting things here: I believe the folks at Digitool read
info-dylan-digest. As I've continued to flame (or at least simmer)
about, the newsgroup and mailing list no longer mirror each other,
so you can't assume that all Dylan interested-folk will see your message
if you just post it to the Newsgroup.
-Andrew