akw@osupyr.UUCP (04/07/87)
To whoever posted that article about the PD C-Compiler in, uh, those early few days of April: 'Fess up. Were you just pulling our respective legs or do you have the goods? If so, *please* post that baby...it could save a few thousand of us the pain of spending $199+ for the sillyness of buying a C compiler. (that costs, oh, 1/3 the price that I bought my machine for [~$589]) Gee, does any one have a PD...Desktop Publishing package...yeah, that's the ticket...with PostScript support...yeah, with a discount coupon for an Atari laser printer...yeah...with a half-tone of Morgan Fairchild on the disk... Andy Weaver / akw@osupyr.UUCP / 614.293.1195 or .292.1741 The Ohio State University / Columbus, OH / "Go Bucks." "Like cold water to the bones, so is good news from a distant land." Prov25.25 Disclaimer: If Ohio State knew I had UseNet access, they would probably have to ask what exactly UseNet is. And how much they should charge.
john@viper.UUCP (04/08/87)
In article <174@osupyr.UUCP> akw@.UUCP (FarOff MicroDesigns) writes: > >To whoever posted that article about the PD C-Compiler in, uh, those >early few days of April: > >'Fess up. Were you just pulling our respective legs or do you have the >goods? If so, *please* post that baby...it could save a few thousand of >us the pain of spending $199+ for the sillyness of buying a C compiler. > >(that costs, oh, 1/3 the price that I bought my machine for [~$589]) > The creature does, in fact, exist. Unfortuntely, even though it's an excelent first-round attempt, I decided I wouldn't want to use it for any significant work. (Significant = anything over 100 lines of code) The compiler does work, but since it doesn't support all the features -I- personaly use in normal development work I can't use it. Sorry, if you plan on doing serious work on the ST in C, you'll still need to get a non-PD compiler... On the other hand, if you're looking for a good inexpensive learning tool, by all means, get it if you can. (Sorry I can't send it to you. I don't have the archive any more.) > >Gee, does any one have a PD...Desktop Publishing package...yeah, that's >the ticket...with PostScript support...yeah, with a discount coupon >for an Atari laser printer...yeah...with a half-tone of Morgan Fairchild >on the disk... > 'Fess up. Are you just pulling our respective legs or do yo have the goods? If so, *please* post that baby...it could save a few thousand of us the pain of spending $149+ for the sillyness of buying a.... ;-) --- John Stanley (john@viper.UUCP) Software Consultant - DynaSoft Systems UUCP: ...{amdahl,ihnp4,rutgers}!{meccts,dayton}!viper!john
bds@mtgzz.UUCP (04/10/87)
In article <797@viper.UUCP>, john@viper.UUCP (John Stanley) writes: > The creature does, in fact, exist. Unfortuntely, even though it's an > excelent first-round attempt, I decided I wouldn't want to use it for > any significant work. (Significant = anything over 100 lines of code) > The compiler does work, but since it doesn't support all the features > -I- personaly use in normal development work I can't use it. Having used the SHAREWARE C compiler, I can say that its much better than the impression this passage leaves. It IS true that no resource editor included, floating point is not supported, initializing is not well supported, and that the standard library is limited in scope. Even so, -I- HAVE done significant work with the compiler, which has resulted in my having written additional support libraries (which I have given to the author): a complete printf, vdi commands, complete string library, getopt(), setjmp(), longjmp(), etc. I hope to provide a gemdos header file soon that is compatable with those provided with other C compilers (limited by my not having any other C compiler to compare against). The AMAZING thing about this compiler is that it CAN run on a unexpanded 520 with a single sided drive, AND there is room for a RAM disk to improve performance. That is the way I used the compiler until I bought a hard disk. I am working on two projects using this compiler: a command shell that gives the feel of the Korn shell (history, emacs editing), and has a set of commonly used programs built in (cat, simple grep, ls, df, echo, cp, mv, etc.) to improve performance and save on space. This is almost complete (currently adding if statements and loops), and when complete will amount to a LOT more than a 100 lines. The second one is a long term project for a chess database, that uses the mouse to move chess pieces on the board or set up a position, and will query the database. This uses vdi for drawing the board and moving the chess pieces, and a window for scrolling through text representing the continuation (ala' MCO for you chess fans). Now here I admit that the lack of a resource editor hurts, because I don't know how to program the menu bar from C (any help here?). I am currently using key sequences for command input (good for an expert mode), and may have to resort to dial buttons (*sigh*). It is within the power of us users to make this a tool a real winner by writing and sharing libraries, header files, and utilities.