I was hoping someone might be kind enough to take the time to explain my problem with orca/m and macgen to me. I’ve always used merlin for assembly; I purchased the orca languages years ago but never used orca/m really; i was more interested in orca/c for toolbox programming, never got very far.
Recently using merlin I was wishing I could step through the code so thought I would try orca/m and gsbug. I have orca/m 2.1.0 installed and started going through the orca/m manual not realizing it was written for v2.0 and so the hello.asm example inthe manual produces no output under v2.1.0. I took me a while to figure that out. So being curious I installed v2.0 and v2.0.4 on a hd partition and v2.0 works as the manual states. v2.0.4 however does not.
So, the crux of it is, v2.0.4 (shell v2.0.3, macgen v2.0.2), macgen does not accept the input:processes that file, prompts for an outfile, then lists a bunch of unfound macros and prompts for a macro file name. If I then enter “13:orcainclude:m=“ macgen is very happy with that and completes and writes out hello.macros. Still won’t produce
“macgen hello.asm hello.macros 13:orcainclude:m=“ but prompts for a filename. Entering “13:orcainclude:m=“ results in “:HD6:ORCA.2.0.4:LIBRARIES:orcainclude:m= could not be opened”. If I then enter “13:orcainclude:m16.orca” macgen
Why does macgen 2.0.2 not accept the second two parameters in “macgen hello.asm hello.macros 13:orcainclude:m=“ and when it the prompts for a file name doesnt accept the wildcard = but does accept the wildcard after the second prompt.
It all doesn’t really matter, I’ll be trying to use v2.1.0 anyway but it bothers me it doesn’t work and I can’t figure out why.
Sorry to be so long winded. as an aside; am I mmissing documentation or was the 524 page manual I have and the release notes all that was ever released?
“macgen hello.asm hello.macros 13:orcainclude:m=“ but prompts for a filename. Entering “13:orcainclude:m=“ results in “:HD6:ORCA.2.0.4:LIBRARIES:orcainclude:m= could not be opened”.
For kicks I replaced Magen v2.0.2 with v2.0 and it all works as expected. <shrug>
On Monday, October 17, 2022 at 2:06:18 PM UTC-7, justliketom...@gmail.com wrote:
“macgen hello.asm hello.macros 13:orcainclude:m=“ but prompts for a filename. Entering “13:orcainclude:m=“ results in “:HD6:ORCA.2.0.4:LIBRARIES:orcainclude:m= could not be opened”.Sounds like the wildcard routine can't find anything, so the program acts like you didn't actually give it the final argument, and queries for a name. Curious that it would work if specified on stdin but not the command line.
IIRC, APW/Orca are different from something like UNIX, where the shell processes the wildcards and hands a full list of arguments to the program. APW/Orca hand the wildcard to the program and let it iterate through the possibilities itself. So ifsomething changed in the way wildcards are processed, that could cause things to fail, but you'd expect it to cause most things to fail the same way.
If you "cat 13:orcainclude:m=", do you get a list of macro files from that directory?
Backing up a step: why can't you use GSBug with Merlin?
Tom Thumb,
I use ORCA/M 2.10 heavily, and this is a typical script used to build a file with a resource fork. The two source files are Filename.src and Filename.rez, with the output being an app with the name Filename:
echo "Processing Files .. "
delete FileName
filetype FileName.src $b0 $0003
17/macgen +C FileName.src FileName.macros FileName.macros 13/Ainclude/mm16.= assemble +W +E +T FileName.src keep=FileName
link +b FileName keep=FileName
filetype FileName.rez $b0 $0015
compile +w FileName.rez keep=resources rez=(-type $5e)
copy -r resources FileName
filetype FileName $b3 $db03
bye
Cheers - Ewen
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 491 |
Nodes: | 16 (2 / 14) |
Uptime: | 91:54:45 |
Calls: | 9,679 |
Files: | 13,723 |
Messages: | 6,174,010 |