This is an archive of CompuServe forum messages from 1985 to 1995, as saved in transcripts by John Foust.
Search Results (2,010 messages)
#2764-
AmigaVision
Message #3225
Steve, Not when much of the program lockes into variables, types, procedures, and function defined by the compiler writer. Also, the same structure may not need the same emphasis everywhere it is used. In some cases a variable is only needed for minor reference, where elsewhere in the program it…
#1353-
Maps
Message #1598
Ash, best way is probably to download the maps in GIF format and then use a GIF viewer to see them. I've tried it and it works. Khalid.
AmigaVision
Message #1583
I bought AmigaVision. This is incredible!!! Especially Screen is like NeXT.
#260-
CanDo/SerialManager
Message #322
Mark, I know that James Nelsn of INOVAtronics Tech Support had something working really well with SerialManager 1.1. He could call up bulletin boards and everything with it. Let me ask him what he's got that I could just post up here.
#260-
CanDo/SerialManager
Message #296
A thought (I too had problems with SerialManager1.1, but got it to work once when I experimented; never did anything real serious with it yet though): Are you setting the 'SetCRMode ON', which will send a CR at the end of each SEND? Otherwise you will need to append a…
Scott, I have the old (1986) version of the ROM Kernel (both), Hardware and Intuition Manuals. Do you suppose I will have get new versions once 2.0 becomes available? From the extreme nature of the improvements, I think this may be so. Those manuals were expensive (especially since I bought…
The IQ of a committe is inversely proportional to the sum of the squares of the IQ's of the individual members! ;-> Mike Haynie (who wants to know?)
MSC Version 6.00 on the PC with optimization handles them very differently. It takes about 6 additional instructions to do the array indexing over the pointer based addressing with that compiler, and since I'm attempting to write a multi-term terminal emulator, on a lookup like that, it's going to be…
In general, no compiler is going to show a difference in code generation in what you've shown in 1) compared to what I did. _Both_ versions are basically doing array indexing – mine just happens to do it using [i], and yours does +i. Both constructs do the same thing,…
Thanks, maybe I can reach him on UseNet.
Thanks for the response… 1. Another question: Can we say temp = &(Emulate->StringDesc + i); and avoid the subscript evaluation? Although I'm not using the Manx compiler (and not writing for the Amiga) from what I've seen, most compilers do a much better job with pointer arithmetic than with subscript…
Wow, that's what Lattice does? That looks wrong to me. If you consider the hex constant to be '1b0' (which ANSI says is what it should be…), then it should be chopped into 0xb0, with the 1 being thrown into the bit bucket. I suspect that Lattice is doing it…
Mike, Yes, to the best of my knowledge, octal constants are always 8 bits and checking K&R (2nd Edition) the escape may be followed by 1, 2 or 3 octal digits (it doesn't say may *only* be followed, but that's implied). However, when dealing with hex it states that there…
Good. Hope it's soon. Thanks for at least the "Willing"…
Wayne – I purchased Lattice C 5.05 direct from Lattice a few months ago. Short of actually looking at the disk directory, you can't tell which 5.0 version you have from the disk label. If the compiler includes a "readme.505" file, you have the 5.05 version. Another way of checking…
Well heck, C's what puts a roof over my head, so I'd better have some idea of how it works :^) -Mike
Incidentally, hex character constants can pretty much go on to infinity (well, there are some limits). ANSI didn't say 8 bits or 16 bits or 32 bits, they just said keep goin' till you hit something which isn't hexadecimal. IMHO this is pretty messed up, as almost anybody ever using…
MUCH better than my explanation!!!!!!!!!! ThanksMike Haynie (bought a Quantum; can't find any Quantum Mechanics…)
You are right, of course, given the assumption that hex constants are 8bits only. The problem is that ANSI compatable compilers have to be prepared to deal with 32bit (or is it word sized?) hex constants. (Note: in ANSI usage hex constant is a name for _character_ constant…) If the…
I have all of the above and then some:) Amiga C for beginners is really for beginners. I haven't found a good general book yet, some are good in some areas and weak in others. I have yet to see a complete coverage on devices. The trackdisk and audio devices…
Wayne, The revision numbers should (I would hope) be printed on the diskettes, but I'm not positive of this, as I've received upgrades for the subsequent versions (after 5.0) via patches, rather than complete sets of diskettes. However, I do know that if you run the "lc1" and/or "lc2" programs,…
Gee Rej, octal is great (for people who don't have any thumbs). 🙂 -larry
Hmm… looked for the example I had, Mike, but can't find it. Will let you know if I do, since I was sure I simply treated the CSI char as an unsigned 8 bit value in order to get around the problems. -larry
Ariel, hmm… looks like it might work… I'll play with that.. thanks! Khalid.
Bob, Thanks for the info. The box says 5.0. I haven't cracked it open yet. If I do, where will the revision number be printed/displayed so that I could tell if it is bare 5.0 or 5.0.5? wmc
Don, when I hear octal, somehow my head start spinning ;-
Michael, Get the Programmer's guide to the Amiga, both volumes of the Amiga Programmer's Handbook, the new ROM Kernel Reference manuals (both volumes), the Hardware reference manual, and the Amiga Developer's and Intuition Manuals (if you can get a hold of them). Its expensive stuff, but you'll find yourself going…
Harry, Programmer's Guide to the Amiga by the recently deceased Rob Peck, Amiga C For Beginners (its an Abacus book), and the Kerninghan and Ritchie Language definition, its expensive but worth it. Also, pick up a copy of the ROM kernel reference manuals and the Hardware Reference manual. Good Luck.…
Basically, you can't (at least not in one line). The best optimization I could see for your code would be to say: struct MCS *temp; temp = &(Emulate->StringDesc[i]); if (temp->IString == *State->stringbuffer + State->stringbufferlength))) { if (temp->MString || temp->FString || temp->PSeperator || temp->PNumtype) … You get the idea – basically…
The code works, but I'd like to change it from subscript-based to pointer-based addressing eliminating the [i]'s. I've tried several ways, but I don't get the hang of it. I'm just learning pointer processing and don't know how to use the pointer addressing to address the i'th occurrence of my…
Your code looks OK to me – what exactly is the problem? Are you getting a compiler error or does the code run incorrectly? From what I can see, you are in fact comparing the character at IString with the character at state->stringbuffer+state->stringbufferlenght. As for addressing Mstring, Fstring, etc. you…
There is no such thing as a UBYTE string literals. Stuff between " and " are always thought of as an array of chars. Casting it to a UBYTE * shouldn't change the way the compiler works on escape sequences either. I guess I don't quite follow what you're saying…could…
#Need C Pointer Help…
Message #118777
/* See line 35 below for question. */ struct MCS { char IString; char MString; char FString; char PSeparator; char PNumType; unsigned int Action; }; struct emulate { char TermDesc[31]; struct NUM NumDesc; struct BIN BoolDesc; unsigned int CtrlChar[32]; struct GFX Graphics; int MCS_Count; struct MCS StringDesc[256]; }; EvalControlString(struct emulate…
OOps…. I think I just realized why the UBYTE fixed the problem.. .I would guess that the UBYTE scan of the string would be handled differently by the compiler. Right? Wrong? -larry
Mike, Thanks for the correction. Funny, I fixed the very problem Rej was having by changing char to UBYTE. -larry
C help
Message #118772
Hello John, The example on the switch command you helped me with a ways back works as I hoped it would. Due to this, I was able to continue with my program and get myself into another confusing situation. I hope you won't mind my asking your advice again. What…
Another possibility: use string concatenation. Eg: "\x9b""0 ….other garp" If your hex sequence is gonna be followed by something that happens to be a valid hexadecimal character, this is the easiest way to get around it. -Mike
Sorry, a char is 8 bits, and an unsigned char is also 8 bits. The range of the two is difference, but they have the same number of bits. And C compilers will put in the unsigned bit pattern, even if it don't fit the range i.e. char c; c…
The sequence 0x9b0 _should_ translate to 0x9b30. A char is 7 bits. an unsigned char is 8 bits, and the 0x9b will not fit in a char. -larry
It'd be strange that you got the disks but not the manual. Hmmm…well, call our sales dept. at (800)221-0440 and tell 'em your story. -Mike
Khalid, how about… struct Message * PollGetMsg(msgport) { if (!msgport->mp_MsgList.lh_Head->ln_Succ) return(Remove(msgport->mp_MsgList.lh_Head)); else return(NULL); } This might not be exactly right, but I got the idea from "Lists and Queues" in the Exec manual. Ariel
Rick: When you say you are going "to interlace", do you mean you simply flip the display into interlace, or are you doubling the screen height (from, say, 200 to 400 lines)? If you are running 4 bitplane graphics (16 color), and you change from a 640 x 200 to…
Wayne, If it's v5.05, then it should be ok. If it's less than that, then Lattice was supplying the patches to fix it for free…no idea on what SAS's policy is on the patches. Don
Rej, I make it simple…I use octal rather than hex when it's embedded in a string. Don
Ansi 'C'
Message #118682
It worked great. Also the fact of having the ansi codes available from the amiga user book is very helpful. Thanks again David. Rej
Thanks David, it's good to have an example (easier to assimilate). I'll test it right away. Rej
Micheal, will try 'all' of these possibities! It's great to know that there's more than one way to do it. Thank you for the information. REj
Wayne, If the version is truly 5.0, then it is a pretty buggy product. The current version (prior to the recent 5.1 upgrade) is 5.05, which I have found to be reasonably stable. All of the upgrades from 5.0 to 5.05 were free (from Lattice). I don't know what SAS's…
Humm… I just updated this week. It "was" supposed to have a new manual of some type. But I also updated to Amiga 5.0 so maybe it slipped thru the cracks. How do I get my new one??
No sweat. We just try to keep as international/Multiplatform as possable.
Page 1 of 41