Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.sys.apple2.programmer > #1507 > unrolled thread

Comments on using Merlin Pro relocatable linker?

Back to article view | Back to comp.sys.apple2.programmer

Contents

  Comments on using Merlin Pro relocatable linker? D Finnigan <dog_cow@macgui.com> - 2015-02-19 19:48 +0000
    Re: Comments on using Merlin Pro relocatable linker? Michael J. Mahon <mjmahon@aol.com> - 2015-02-19 16:42 -0600
      Re: Comments on using Merlin Pro relocatable linker? D Finnigan <dog_cow@macgui.com> - 2015-02-19 22:51 +0000
        Re: Comments on using Merlin Pro relocatable linker? Michael J. Mahon <mjmahon@aol.com> - 2015-02-19 17:31 -0600
          Re: Comments on using Merlin Pro relocatable linker? D Finnigan <dog_cow@macgui.com> - 2015-02-20 20:27 +0000
            Re: Comments on using Merlin Pro relocatable linker? "Anton Treuenfels" <teamtempest@yahoo.com> - 2015-02-20 17:16 -0600
              Re: Comments on using Merlin Pro relocatable linker? Michael J. Mahon <mjmahon@aol.com> - 2015-02-21 12:44 -0600
            Re: Comments on using Merlin Pro relocatable linker? Michael J. Mahon <mjmahon@aol.com> - 2015-02-21 12:44 -0600
              Re: Comments on using Merlin Pro relocatable linker? D Finnigan <dog_cow@macgui.com> - 2015-02-21 20:00 +0000
                Re: Comments on using Merlin Pro relocatable linker? Michael J. Mahon <mjmahon@aol.com> - 2015-02-22 01:36 -0600
                  Re: Comments on using Merlin Pro relocatable linker? D Finnigan <dog_cow@macgui.com> - 2015-02-23 17:30 +0000
                    Re: Comments on using Merlin Pro relocatable linker? Michael J. Mahon <mjmahon@aol.com> - 2015-02-23 12:57 -0600
                      Re: Comments on using Merlin Pro relocatable linker? D Finnigan <dog_cow@macgui.com> - 2015-02-23 19:12 +0000
                        Re: Comments on using Merlin Pro relocatable linker? wssimms@gmail.com - 2015-02-23 15:44 -0800
                          Re: Comments on using Merlin Pro relocatable linker? D Finnigan <dog_cow@macgui.com> - 2015-02-27 20:07 +0000
                        Re: Comments on using Merlin Pro relocatable linker? Michael J. Mahon <mjmahon@aol.com> - 2015-02-24 03:16 -0600
                          Re: Comments on using Merlin Pro relocatable linker? D Finnigan <dog_cow@macgui.com> - 2015-02-27 20:11 +0000
    Re: Comments on using Merlin Pro relocatable linker? Hugh Hood <hughhood@earthlink.net> - 2015-02-20 09:59 -0600
      Re: Comments on using Merlin Pro relocatable linker? D Finnigan <dog_cow@macgui.com> - 2015-02-20 20:26 +0000
    Re: Comments on using Merlin Pro relocatable linker? jbrooks@blueshiftinc.com - 2015-09-25 21:18 -0700

#1507 — Comments on using Merlin Pro relocatable linker?

I've started working on a project using Merlin Pro v2.45 on DOS 3.3 with a
platinum Apple IIe. I have already hit the 32KB source code limit on DOS
3.3, and I removed some comments and unused code but of course I'm going to
hit the limit again because my source is still growing. I could switch to
ProDOS, but that only gains me about an extra 10K and eventually I'll hit
that limit too.

So, flipping through the Merlin Pro manual, I've decided to try using the
REL features. I was able to make a little "hello world" demo.

I want to know if anyone out here in net land has experience using the
relocatable linker in Merlin Pro with medium to large size projects and can
offer any remarks or warnings or gotchas with the system.

Thanks.

-- 
]DF$
Apple II Book: http://macgui.com/newa2guide/
Usenet: http://macgui.com/usenet/  <-- get posts by email!
Apple II Web & Blog hosting: http://a2hq.com/

[toc] | [next] | [standalone]

#1508

D Finnigan <dog_cow@macgui.com> wrote:
> I've started working on a project using Merlin Pro v2.45 on DOS 3.3 with a
> platinum Apple IIe. I have already hit the 32KB source code limit on DOS
> 3.3, and I removed some comments and unused code but of course I'm going to
> hit the limit again because my source is still growing. I could switch to
> ProDOS, but that only gains me about an extra 10K and eventually I'll hit
> that limit too.
> 
> So, flipping through the Merlin Pro manual, I've decided to try using the
> REL features. I was able to make a little "hello world" demo.
> 
> I want to know if anyone out here in net land has experience using the
> relocatable linker in Merlin Pro with medium to large size projects and can
> offer any remarks or warnings or gotchas with the system.
> 
> Thanks.

An alternative to linking when source files grow is to split your source
into multiple (hopefully logically related) files and pare your actual
assembly file down to a "use" for macro definitions and a series of "put"s
for the rest of the code segments. 

This way, the "put" segments only occupy space one at a time. 

The ProDOS version is a win, too, and worth the changeover. 
-- 
-michael - NadaNet 3.1 and AppleCrate II: http://home.comcast.net/~mjmahon

[toc] | [prev] | [next] | [standalone]

#1509

Michael J. Mahon wrote:
> 
> An alternative to linking when source files grow is to split your source
> into multiple (hopefully logically related) files and pare your actual
> assembly file down to a "use" for macro definitions and a series of "put"s
> for the rest of the code segments. 

Does PUT require the target file to be saved with the W command? Just from
simple testing, I couldn't get PUT to accept a Merlin .S source file.


> This way, the "put" segments only occupy space one at a time. 
> 
> The ProDOS version is a win, too, and worth the changeover. 
>

Point taken. I just need to dig out my ProDOS User's disk with its Convert
utility.

-- 
]DF$
Apple II Book: http://macgui.com/newa2guide/
Usenet: http://macgui.com/usenet/  <-- get posts by email!
Apple II Web & Blog hosting: http://a2hq.com/

[toc] | [prev] | [next] | [standalone]

#1510

D Finnigan <dog_cow@macgui.com> wrote:
> Michael J. Mahon wrote:
>> 
>> An alternative to linking when source files grow is to split your source
>> into multiple (hopefully logically related) files and pare your actual
>> assembly file down to a "use" for macro definitions and a series of "put"s
>> for the rest of the code segments. 
> 
> Does PUT require the target file to be saved with the W command? Just from
> simple testing, I couldn't get PUT to accept a Merlin .S source file.
> 
> 
>> This way, the "put" segments only occupy space one at a time. 
>> 
>> The ProDOS version is a win, too, and worth the changeover. 
>> 
> 
> Point taken. I just need to dig out my ProDOS User's disk with its Convert
> utility.


Put without the .s suffix. 
-- 
-michael - NadaNet 3.1 and AppleCrate II: http://home.comcast.net/~mjmahon

[toc] | [prev] | [next] | [standalone]

#1513

Michael J. Mahon wrote:
> D Finnigan <dog_cow@macgui.com> wrote:
>> Michael J. Mahon wrote:
>>> 
>>> An alternative to linking when source files grow is to split your source
>>> into multiple (hopefully logically related) files and pare your actual
>>> assembly file down to a "use" for macro definitions and a series of
>>> "put"s
>>> for the rest of the code segments. 
>> 
>> Does PUT require the target file to be saved with the W command? Just
>> from
>> simple testing, I couldn't get PUT to accept a Merlin .S source file.
>> 
>> 
>>> This way, the "put" segments only occupy space one at a time. 
>>> 
>>> The ProDOS version is a win, too, and worth the changeover. 
>>> 
>> 
>> Point taken. I just need to dig out my ProDOS User's disk with its
>> Convert
>> utility.
> 
> 
> Put without the .s suffix. 

Thanks.

Also, but suggesting that I use PUT, are you also implying that I should
stay away from using the REL linker?

[toc] | [prev] | [next] | [standalone]

#1514

"D Finnigan" <dog_cow@macgui.com> wrote in message 
news:dog_cow-1424464090@macgui.com...
> Michael J. Mahon wrote:
>> D Finnigan <dog_cow@macgui.com> wrote:
>>> Michael J. Mahon wrote:
>>>>
>>>> An alternative to linking when source files grow is to split your 
>>>> source
>>>> into multiple (hopefully logically related) files and pare your actual
>>>> assembly file down to a "use" for macro definitions and a series of
>>>> "put"s
>>>> for the rest of the code segments.
>>>
>>> Does PUT require the target file to be saved with the W command? Just
>>> from
>>> simple testing, I couldn't get PUT to accept a Merlin .S source file.
>>>
>>>
>>>> This way, the "put" segments only occupy space one at a time.
>>>>
>>>> The ProDOS version is a win, too, and worth the changeover.
>>>>
>>>
>>> Point taken. I just need to dig out my ProDOS User's disk with its
>>> Convert
>>> utility.
>>
>>
>> Put without the .s suffix.
>
> Thanks.
>
> Also, but suggesting that I use PUT, are you also implying that I should
> stay away from using the REL linker?


I can't speak for Michael, but I doubt it. I've used both USE and PUT with 
Merlin for the Commodore 64 for source that was too large to fit in memory 
at once. At the time there was no REL available, ie., USE and PUT both 
pre-date versions of Merlin that also had REL. The main drawback was greatly 
reduced assembly speed versus in-memory assembly,  a problem emphasized on 
the C64 by its slow drive transfer rates. An unexpected advantage was that 
use of PUT made it reasonable to divide source modules by purpose, rather 
than have everything in one big file.

Merlin for the C128 did have REL, and I did play around with it. The main 
advantage of REL over PUT is assembly speed. Once a REL file is created it 
doesn't need to be assembled again to be incorporated into a project, unlike 
a PUT file, which is re-assembled from scratch every time it is used.

Just my $0.02.

- Anton Treuenfels 

[toc] | [prev] | [next] | [standalone]

#1515

"Anton Treuenfels" <teamtempest@yahoo.com> wrote:
> "D Finnigan" <dog_cow@macgui.com> wrote in message news:dog_cow-1424464090@macgui.com...
>> Michael J. Mahon wrote:
>>> D Finnigan <dog_cow@macgui.com> wrote:
>>>> Michael J. Mahon wrote:
>>>>> 
>>>>> An alternative to linking when source files grow is to split your >>>> source
>>>>> into multiple (hopefully logically related) files and pare your actual
>>>>> assembly file down to a "use" for macro definitions and a series of
>>>>> "put"s
>>>>> for the rest of the code segments.
>>>> 
>>>> Does PUT require the target file to be saved with the W command? Just
>>>> from
>>>> simple testing, I couldn't get PUT to accept a Merlin .S source file.
>>>> 
>>>> 
>>>>> This way, the "put" segments only occupy space one at a time.
>>>>> 
>>>>> The ProDOS version is a win, too, and worth the changeover.
>>>>> 
>>>> 
>>>> Point taken. I just need to dig out my ProDOS User's disk with its
>>>> Convert
>>>> utility.
>>> 
>>> 
>>> Put without the .s suffix.
>> 
>> Thanks.
>> 
>> Also, but suggesting that I use PUT, are you also implying that I should
>> stay away from using the REL linker?
> 
> 
> I can't speak for Michael, but I doubt it. I've used both USE and PUT
> with Merlin for the Commodore 64 for source that was too large to fit in
> memory at once. At the time there was no REL available, ie., USE and PUT
> both pre-date versions of Merlin that also had REL. The main drawback was
> greatly reduced assembly speed versus in-memory assembly,  a problem
> emphasized on the C64 by its slow drive transfer rates. An unexpected
> advantage was that use of PUT made it reasonable to divide source modules
> by purpose, rather than have everything in one big file.
> 
> Merlin for the C128 did have REL, and I did play around with it. The main
> advantage of REL over PUT is assembly speed. Once a REL file is created
> it doesn't need to be assembled again to be incorporated into a project,
> unlike a PUT file, which is re-assembled from scratch every time it is used.
> 
> Just my $0.02.
> 
> - Anton Treuenfels

With a hard disk and a Zip Chip, or an emulator, assembly speed never
bothered me. In fact, it's nice to have a few seconds to think about what
you've done. ;-)
-- 
-michael - NadaNet 3.1 and AppleCrate II: http://home.comcast.net/~mjmahon

[toc] | [prev] | [next] | [standalone]

#1516

D Finnigan <dog_cow@macgui.com> wrote:
> Michael J. Mahon wrote:
>> D Finnigan <dog_cow@macgui.com> wrote:
>>> Michael J. Mahon wrote:
>>>> 
>>>> An alternative to linking when source files grow is to split your source
>>>> into multiple (hopefully logically related) files and pare your actual
>>>> assembly file down to a "use" for macro definitions and a series of
>>>> "put"s
>>>> for the rest of the code segments. 
>>> 
>>> Does PUT require the target file to be saved with the W command? Just
>>> from
>>> simple testing, I couldn't get PUT to accept a Merlin .S source file.
>>> 
>>> 
>>>> This way, the "put" segments only occupy space one at a time. 
>>>> 
>>>> The ProDOS version is a win, too, and worth the changeover. 
>>>> 
>>> 
>>> Point taken. I just need to dig out my ProDOS User's disk with its
>>> Convert
>>> utility.
>> 
>> 
>> Put without the .s suffix. 
> 
> Thanks.
> 
> Also, but suggesting that I use PUT, are you also implying that I should
> stay away from using the REL linker?

No, but since your only problem is size, PUT deals with it in a very simple
way without the additional complications of linking. And it keeps your
listing whole. 

I've always preferred to keep my programs as single assemblies, both for
the listing and for a trivial "make".
-- 
-michael - NadaNet 3.1 and AppleCrate II: http://home.comcast.net/~mjmahon

[toc] | [prev] | [next] | [standalone]

#1517

Michael J. Mahon wrote:
> D Finnigan <dog_cow@macgui.com> wrote:
>> Michael J. Mahon wrote:
>>> D Finnigan <dog_cow@macgui.com> wrote:
>>>> Michael J. Mahon wrote:
>>>>> 
>>>>> An alternative to linking when source files grow is to split your
>>>>> source
>>>>> into multiple (hopefully logically related) files and pare your actual
>>>>> assembly file down to a "use" for macro definitions and a series of
>>>>> "put"s
>>>>> for the rest of the code segments. 
>>>> 
>>>> Does PUT require the target file to be saved with the W command? Just
>>>> from
>>>> simple testing, I couldn't get PUT to accept a Merlin .S source file.
>>>> 
>>>> 
>>>>> This way, the "put" segments only occupy space one at a time. 
>>>>> 
>>>>> The ProDOS version is a win, too, and worth the changeover. 
>>>>> 
>>>> 
>>>> Point taken. I just need to dig out my ProDOS User's disk with its
>>>> Convert
>>>> utility.
>>> 
>>> 
>>> Put without the .s suffix. 
>> 
>> Thanks.
>> 
>> Also, but suggesting that I use PUT, are you also implying that I should
>> stay away from using the REL linker?
> 
> No, but since your only problem is size, PUT deals with it in a very
> simple
> way without the additional complications of linking. And it keeps your
> listing whole. 

OK, thanks for the clarification.

Also, I've discovered why my experiment with PUT failed: the DOS 3.3 version
of Merlin Pro *requires* the target file to be a text file saved with the W
command, whereas under ProDOS Merlin Pro, all files are text files.

But this isn't the first time that the Merlin Pro manual has been unclear or
vague about a particular function of the program. :-(

Needless to say, I'm going to be switching over to ProDOS Merlin Pro ASAP.


-- 
]DF$
Apple II Book: http://macgui.com/newa2guide/
Usenet: http://macgui.com/usenet/  <-- get posts by email!
Apple II Web & Blog hosting: http://a2hq.com/

[toc] | [prev] | [next] | [standalone]

#1518

D Finnigan <dog_cow@macgui.com> wrote:
> Michael J. Mahon wrote:
>> D Finnigan <dog_cow@macgui.com> wrote:
>>> Michael J. Mahon wrote:
>>>> D Finnigan <dog_cow@macgui.com> wrote:
>>>>> Michael J. Mahon wrote:
>>>>>> 
>>>>>> An alternative to linking when source files grow is to split your
>>>>>> source
>>>>>> into multiple (hopefully logically related) files and pare your actual
>>>>>> assembly file down to a "use" for macro definitions and a series of
>>>>>> "put"s
>>>>>> for the rest of the code segments. 
>>>>> 
>>>>> Does PUT require the target file to be saved with the W command? Just
>>>>> from
>>>>> simple testing, I couldn't get PUT to accept a Merlin .S source file.
>>>>> 
>>>>> 
>>>>>> This way, the "put" segments only occupy space one at a time. 
>>>>>> 
>>>>>> The ProDOS version is a win, too, and worth the changeover. 
>>>>>> 
>>>>> 
>>>>> Point taken. I just need to dig out my ProDOS User's disk with its
>>>>> Convert
>>>>> utility.
>>>> 
>>>> 
>>>> Put without the .s suffix. 
>>> 
>>> Thanks.
>>> 
>>> Also, but suggesting that I use PUT, are you also implying that I should
>>> stay away from using the REL linker?
>> 
>> No, but since your only problem is size, PUT deals with it in a very
>> simple
>> way without the additional complications of linking. And it keeps your
>> listing whole. 
> 
> OK, thanks for the clarification.
> 
> Also, I've discovered why my experiment with PUT failed: the DOS 3.3 version
> of Merlin Pro *requires* the target file to be a text file saved with the W
> command, whereas under ProDOS Merlin Pro, all files are text files.
> 
> But this isn't the first time that the Merlin Pro manual has been unclear or
> vague about a particular function of the program. :-(
> 
> Needless to say, I'm going to be switching over to ProDOS Merlin Pro ASAP.

Sounds good!

I also realized that a major reason I like one big happy absolute assembly
is that the listing shows the actual addresses of everything.  ;-)
-- 
-michael - NadaNet 3.1 and AppleCrate II: http://home.comcast.net/~mjmahon

[toc] | [prev] | [next] | [standalone]

#1519

Michael J. Mahon wrote:
> 
> Sounds good!
> 
> I also realized that a major reason I like one big happy absolute assembly
> is that the listing shows the actual addresses of everything.  ;-)

Yes, that is useful for debugging.

I used the DOS 3.3 -> ProDOS converter from the ProDOS 1.0.1 User's Disk.
Had to patch the clock year table. That went well.

The actual conversion, however, was quite unpleasant. At some point during
the conversion, my DOS 3.3 source files got corrupted on the disk. Then I
discovered that the ProDOS Merlin has some little differences from the DOS
3.3 version that I don't like.

Fortunately, I had a recent backup copy of my DOS 3.3 source disk, so I only
lost a few minor changes.

-- 
]DF$
Apple II Book: http://macgui.com/newa2guide/
Usenet: http://macgui.com/usenet/  <-- get posts by email!
Apple II Web & Blog hosting: http://a2hq.com/

[toc] | [prev] | [next] | [standalone]

#1520

D Finnigan <dog_cow@macgui.com> wrote:
> Michael J. Mahon wrote:
>> 
>> Sounds good!
>> 
>> I also realized that a major reason I like one big happy absolute assembly
>> is that the listing shows the actual addresses of everything.  ;-)
> 
> Yes, that is useful for debugging.
> 
> I used the DOS 3.3 -> ProDOS converter from the ProDOS 1.0.1 User's Disk.
> Had to patch the clock year table. That went well.
> 
> The actual conversion, however, was quite unpleasant. At some point during
> the conversion, my DOS 3.3 source files got corrupted on the disk. Then I
> discovered that the ProDOS Merlin has some little differences from the DOS
> 3.3 version that I don't like.
> 
> Fortunately, I had a recent backup copy of my DOS 3.3 source disk, so I only
> lost a few minor changes.

It's been so long since I used the DOS version that I'm curious about the
changes you don't like...
-- 
-michael - NadaNet 3.1 and AppleCrate II: http://home.comcast.net/~mjmahon

[toc] | [prev] | [next] | [standalone]

#1521

Michael J. Mahon wrote:
> 
> It's been so long since I used the DOS version that I'm curious about the
> changes you don't like...
>

They're probably little things that can be changed using the parameters
file. I need to read through that section of my manual.

But under my present DOS 3.3 system, I can just hit D to change to drive 2
where my source files are. I'm hoping ProDOS Merlin can have a default path.

Second, I can press Q from the main menu to exit DOS 3.3 Merlin, whereas
ProDOS Merlin asks for confirmation to quit.

Third, I can type ASSEM from a BASIC or Monitor prompt to warm-start Merlin.

-- 
]DF$
Apple II Book: http://macgui.com/newa2guide/
Usenet: http://macgui.com/usenet/  <-- get posts by email!
Apple II Web & Blog hosting: http://a2hq.com/

[toc] | [prev] | [next] | [standalone]

#1522

You set the default path by using the prodos prefix command after pressing 'd' (I think) to enter a disk command.

As far as returning to Merlin I always just returned to the prodos launcher and relaunched Merlin from there. Not as convenient as ASSEM, but easy enough

[toc] | [prev] | [next] | [standalone]

#1531

wssimms wrote:
> You set the default path by using the prodos prefix command after pressing
> 'd' (I think) to enter a disk command.
> 
> As far as returning to Merlin I always just returned to the prodos
> launcher
> and relaunched Merlin from there. Not as convenient as ASSEM, but easy
> enough

Actually, now that I think of it, that method could be faster if I used a
ProDOS program menu. I could potentially save 4  keystrokes to relaunch
Merlin.

[toc] | [prev] | [next] | [standalone]

#1523

D Finnigan <dog_cow@macgui.com> wrote:
> Michael J. Mahon wrote:
>> 
>> It's been so long since I used the DOS version that I'm curious about the
>> changes you don't like...
>> 
> 
> They're probably little things that can be changed using the parameters
> file. I need to read through that section of my manual.

Me, too. 

> But under my present DOS 3.3 system, I can just hit D to change to drive 2
> where my source files are. I'm hoping ProDOS Merlin can have a default path.

Yes, typing "d pfx work/synth" is, for me, a little salutation to the work
at hand. It kind of puts me in the mood...

> Second, I can press Q from the main menu to exit DOS 3.3 Merlin, whereas
> ProDOS Merlin asks for confirmation to quit.

Ever had that sinking feeling after one stray keystroke leaves you briefly
in OMG-land?

> Third, I can type ASSEM from a BASIC or Monitor prompt to warm-start Merlin.

I guess I don't often leave the assembler, and when I do, I'm likely just
to reboot. ;-)
-- 
-michael - NadaNet 3.1 and AppleCrate II: http://home.comcast.net/~mjmahon

[toc] | [prev] | [next] | [standalone]

#1532

Michael J. Mahon wrote:
> D Finnigan <dog_cow@macgui.com> wrote:
>> Michael J. Mahon wrote:
>>> 
>>> It's been so long since I used the DOS version that I'm curious about
>>> the
>>> changes you don't like...
>>> 
>> 
>> They're probably little things that can be changed using the parameters
>> file. I need to read through that section of my manual.
> 
> Me, too. 

Well, I did, and I was disappointed. The parameters are for diddly-do things
like 80-columns display and beeping the speaker.

> 
>> But under my present DOS 3.3 system, I can just hit D to change to drive
>> 2
>> where my source files are. I'm hoping ProDOS Merlin can have a default
>> path.
> 
> Yes, typing "d pfx work/synth" is, for me, a little salutation to the work
> at hand. It kind of puts me in the mood...
> 
>> Second, I can press Q from the main menu to exit DOS 3.3 Merlin, whereas
>> ProDOS Merlin asks for confirmation to quit.
> 
> Ever had that sinking feeling after one stray keystroke leaves you briefly
> in OMG-land?

I don't make stray keystrokes. ;-) True story: I have two Apples with the
Ctrl-Reset slide switch on their encoder board 
and I always have this switch set so I can do a single-key Reset.


Thanks for your input, everyone. I'm using PUT files now. I've posted some
of my project on Mac GUI. More to come soon, I hope.

-- 
]DF$
Apple II Book: http://macgui.com/newa2guide/
Usenet: http://macgui.com/usenet/  <-- get posts by email!
Apple II Web & Blog hosting: http://a2hq.com/

[toc] | [prev] | [next] | [standalone]

#1511

David:

I respect your 'purist' approach in that you are staying with the Apple IIe
to assemble your Merlin files.

But ...

If the project is more important that the method, may I suggest you try
assembling those big files with Brutal Deluxe's Merlin 32?

I like heavily to comment my Merlin source files and since there is no file
size limit with Merlin 32, I can do just that and not worry.

Another benefit --

Unlike the source code of most of the pros here, my source code rarely
assembles without errors the first (second, third, forth) time through. With
Merlin 32, I can actually read the error messages easily (they scroll off
the screen too quickly on an Apple II emulator, and the space bar doesn't
always work to stop it in time), while at the same time (in another window)
have the source code ready to modify and save for another crack at
'perfection'. I use BBEdit with a modified version of Ivan Drucker's 6502
Language Module (for syntax coloring) for that, but any text editor will
work.

FWIW, I wrote a couple of simple Unix 'filters' and AppleScripts for BBEdit
that convert both to and from Merlin (high bit) files. Merlin 32 requires
'normal' low-bit ASCII and UNIX (LF only) line termination. If someone would
like to see those filters, let me know. Believe me, they're not rocket
surgery. :-)

Again, though, I do appreciate your trying to keep it all on the Apple II.
Just my 2 cents. And thanks, Ivan. Without your pattern to go by, I'd have
been lost on that Language Module.






Hugh Hood




in article dog_cow-1424375335@macgui.com, D Finnigan at dog_cow@macgui.com
wrote on 2/19/15 1:48 PM:

> I've started working on a project using Merlin Pro v2.45 on DOS 3.3 with a
> platinum Apple IIe. I have already hit the 32KB source code limit on DOS
> 3.3, and I removed some comments and unused code but of course I'm going to
> hit the limit again because my source is still growing. I could switch to
> ProDOS, but that only gains me about an extra 10K and eventually I'll hit
> that limit too.
> 
> So, flipping through the Merlin Pro manual, I've decided to try using the
> REL features. I was able to make a little "hello world" demo.
> 
> I want to know if anyone out here in net land has experience using the
> relocatable linker in Merlin Pro with medium to large size projects and can
> offer any remarks or warnings or gotchas with the system.
> 
> Thanks.

[toc] | [prev] | [next] | [standalone]

#1512

Hugh Hood wrote:
> David:
> 
> I respect your 'purist' approach in that you are staying with the Apple
> IIe
> to assemble your Merlin files.
> 
> Again, though, I do appreciate your trying to keep it all on the Apple II.
> Just my 2 cents. 

I'm writing code for the Uthernet.

[toc] | [prev] | [next] | [standalone]

#1807

On Thursday, February 19, 2015 at 11:48:57 AM UTC-8, D Finnigan wrote:
> I've started working on a project using Merlin Pro v2.45 on DOS 3.3 with a
> platinum Apple IIe. I have already hit the 32KB source code limit on DOS
> 3.3, and I removed some comments and unused code but of course I'm going to
> hit the limit again because my source is still growing. I could switch to
> ProDOS, but that only gains me about an extra 10K and eventually I'll hit
> that limit too.
> 
> So, flipping through the Merlin Pro manual, I've decided to try using the
> REL features. I was able to make a little "hello world" demo.
> 
> I want to know if anyone out here in net land has experience using the
> relocatable linker in Merlin Pro with medium to large size projects and can
> offer any remarks or warnings or gotchas with the system.
> 
> Thanks.
> 
> -- 
> ]DF$
> Apple II Book: http://macgui.com/newa2guide/
> Usenet: http://macgui.com/usenet/  <-- get posts by email!
> Apple II Web & Blog hosting: http://a2hq.com/

I know this is awhile back, but I have done large projects with Merlin 8 & 16, using REL to assemble each src file into it's own binary, and then having a linker script with LKV 00 and a bunch or ORG/LNK/SAV chunks to write out multiple binary blocks at different org addresses.

-JB

[toc] | [prev] | [standalone]

Back to top | Article view | comp.sys.apple2.programmer

csiph-web