[Coco] OS-9 Library generation

Wed May 13 00:14:40 EDT 2015

I do not see either "merge" or "cat" in CMDS for my last OS-9 Level-II system.  (1/11/1993)

OS9GEN may have been the only option back in 1986 but as you say a 40 mm cannon for very simple merges. 

Not everything on CI$ made it to Delphi. The OS-9 Level-II new files were few and far between at the end when the Delphi OS-9 forum was heavily dominated by the OSK folks. (Was CI$ also?)
----------------------------------- 

I would like to hear Willard's comments about what you want to make standard. 

I was trying to make it easier for the first time "C" programmer and present it similar to what Tandy offered. I hope you will add your "new" (Very few changes / additions) to "my" C Compiler project as a .dsk file.

-----------------------------------

One of my goals that the inverse appears to be the dominate goal of others is to make it as simple as possible for new users.

Yes you may have a fast great system but think about the new user who opens up the OS-9 Manual and the "C" Compiler disk and is told about your system and they do not match at all.

Give up, perhaps CoCo OS-9 is not the best option for them.

-----------------------------------

I have been thinking where OS-9 people could ask questions and get help.

YES, OS-9. I have an unproven theory that there are very many out there.

1) [CoCo], too much NitrOS-9 dominated. 

2) http://www.tandycoco.com/forum/ also too much NitrOS-9 dominated.

3) Facebook, too many pictures of what was just found. Way too much traffic and not archived which was just now a discussion on Facebook.

4) Another Forum that was just started? Needs to be looked at to see if that might be the way to go.

Problems, cutting the [CoConut] pie into more pieces.

I just can't handle any more projects.

SHF

----- Original Message ----- 
From: "Bill Pierce via Coco" <coco at maltedmedia.com>
To: <coco at maltedmedia.com>
Cc: "Bill Pierce" <ooogalapasooo at aol.com>
Sent: Tuesday, May 12, 2015 8:19 PM
Subject: Re: [Coco] OS-9 Library generation

...
> 
> The components to my current C compiler are listed and well documented on my website on the "MJK C Compiler System" page.
> I have currently discontinued use of c.prep19b, and reverted back to the old MW c.prep because c.prep19b pukes on very long lines in the sources and allocated memory was cut to make room for features (it's in the docs). The changes made in my C system are as follows:
> 
...
> Bill Pierce
> "Charlie stole the handle, and the train it won't stop going, no way to slow down!" - Ian Anderson - Jethro Tull
> 
> 
> 
> My Music from the Tandy/Radio Shack Color Computer 2 & 3
> https://sites.google.com/site/dabarnstudio/
> Co-Contributor, Co-Editor for CocoPedia
> http://www.cocopedia.com/wiki/index.php/Main_Page
> Global Moderator for TRS-80/Tandy Color Computer Forums
> http://www.tandycoco.com/forum/
> 
> E-Mail: ooogalapasooo at aol.com
> 
> 
> 
> 
> 
> 
> -----Original Message-----
> From: Stephen H. Fischer <SFischer1 at Mindspring.com>
> To: CoCoList for Color Computer Enthusiasts <coco at maltedmedia.com>
> Sent: Tue, May 12, 2015 9:52 pm
> Subject: Re: [Coco] OS-9 Library generation
> 
> 
> You have the 40mm cannon pointed in the wrong direction.
> 
> The routine I used
> to split the library I think also wrote a text file with the names of the
> modules in the library.
> 
> Facing doing a merge of 40 - 70 modules and perhaps
> doing it with several merges hopefully using a ShellPlus script was something
> that could not be done successfully even with a list of the modules in the
> proper order. That was the 40mm cannon pointing at the project.
> 
> As I was
> building System disks using OS9GEN and could edit text files at that point the
> OS9GEN solution presented itself and worked quite nicely.
> 
> All I needed to do
> was to change one number in the "abort" module so the entire program I was
> trying to fix was included in the "Core" dump. 
> 
> The bug made the "core" dump
> short by one (1).  Thus constant problems looking at the "Core" dump and the
> C.Link generated loader map. (WHAT? C.Link generates loader maps!)
> 
> I doubt if
> you care but I have attached Abort.zip to this e-mail. Dated 7/1/1986.
> 
> I am
> unsure if the fix is in this file but every library in use "may" have this bug
> except the ones I made and used.
> 
> ------------------------
> 
> I do not think
> "Make" was on my radar at that point but if the entire library needed to be
> assembled / compiled Make would be the only way to go. I started using "Make" as
> soon as I saw it. 
> 
> It's the use of OS9GEN with the file list in a simple text
> file was what I wanted to add. 
> 
> ------------------------
> 
> The second phase
> of the C Complier project that I never finished was for lack of directions from
> any direction for what to include.
> 
> You perhaps are doing that phase, one that
> needs to be done. There are way too many versions of libs available and no clear
> instructions.
> 
> Willard just listed all the libraries available and I did not
> figure out a plan.
> 
> http://www.tandycoco.com/forum/viewtopic.php?p=528#p528
> 
> 
> Adding your final .dsk(s) and how you chose what to include would make the
> project complete.
> 
> SHF
> 
> ----- Original Message ----- 
> From: "Bill Pierce
> via Coco" <coco at maltedmedia.com>
> To: <coco at maltedmedia.com>
> Cc: "Bill Pierce"
> <ooogalapasooo at aol.com>
> Sent: Monday, May 11, 2015 11:28 PM
> Subject: Re:
> [Coco] OS-9 Library generation
> 
> 
>> Stephen, I using sources to make "new"
> libraries, not fix old ones. So your 40mm cannon to kill a mouse technique is
> useless. A makefile is much simpler and more efficient.
>> 
>> 
>> 
>> 
>> 
>>
> Bill Pierce