--------------- FIDO MESSAGE AREA==> TOPIC: 107 PASCAL Ref: FA100006 Date: 05/19/98 From: RICKEY PARRISH Time: 09:32pm \/To: JASEN BETTS (Read 1 times) Subj: CGI JB> In pascal if you don't use CRT read (readln etc) will JB> read from STDIN, if you JB> DO use CRT open a file called '' for reading, that's STDIN too. Ok thanks. I'll have to try that. --- Maximus/2 2.02 * Origin: T-Shirts 'N Genes BBS Duncan Canada (250) 748-3408 (1:340/204) --------------- FIDO MESSAGE AREA==> TOPIC: 107 PASCAL Ref: FA100007 Date: 05/19/98 From: RICKEY PARRISH Time: 09:35pm \/To: BEN CAVANAGH (Read 1 times) Subj: CGI BC> I'm off topic but the good answer is : BC> Ron McGovney, Dave Mustaine, James Hetfield, Lars Ulrich Ive heard Ron's name before, but I never knew he was actually in the band. Have to change that :) BC> If you have access to Internet visit www.yahoo.com BC> and go to CGI section BC> they give example how to write CGI with Pascal Ok, thanks. I never even thought of using yahoo. I went to www.cgi-resources.com, but they dont have any pascal stuff. Just C and Perl and a few others. --- Maximus/2 2.02 * Origin: T-Shirts 'N Genes BBS Duncan Canada (250) 748-3408 (1:340/204) --------------- FIDO MESSAGE AREA==> TOPIC: 107 PASCAL Ref: FA100008 Date: 05/19/98 From: JASEN BETTS Time: 05:32pm \/To: SIMON STONE (Read 1 times) Subj: EXEC - PKZIP/UNZIP hP SS> KF>> Exec(GetEnv('COMSPEC'),'/C SS> '+FSearch('PKZIP.EXE',GetEnv('PATH'))+' KF> >> NUL'); SS> SS> JB> UMM... you don't need fsearch, the COMSPEC prog takes care of SS> that. SS> No it dosn't, COMSPEC gets the path and filename to COMMAND.COM or the SS> operating system command file !! that's what I said, ("the comspec prog"). COMMAND.COM has it's own version of fsearch built in (try it) :) --- EzyQwk V1.20 01fa018d * Origin: CSS Brisbane, Qld, Australia. (61-7-3367-3890) (3:640/350) --------------- FIDO MESSAGE AREA==> TOPIC: 107 PASCAL Ref: FA100009 Date: 05/19/98 From: JASEN BETTS Time: 05:40pm \/To: DAVID CHORD (Read 1 times) Subj: Handling linked lists DC> Comments : Array [1..120] of string [100] DC> DC> Which is approx 13.5k/record. yeah, fixed size records are easier to handle but they sure do waste space. will you be storing them in the file in a packed format? DC> I'm doing a bit of study into what I can on lists, bu will definetly DC> need some help on this. DC> DC> Anyone? Please? I'll do what I can. --- EzyQwk V1.20 01fa018d * Origin: CSS Brisbane, Qld, Australia. (61-7-3367-3890) (3:640/350) --------------- FIDO MESSAGE AREA==> TOPIC: 107 PASCAL Ref: FA100010 Date: 05/19/98 From: JASEN BETTS Time: 05:43pm \/To: STEVE JOHNSON (Read 1 times) Subj: Help me! SJ> JB>why must they be stored that way? can you store them SJ> "pre-calculated" >instead, or aswell? SJ> SJ> It's a pascal data file. And the array is quite large, and well, I'm SJ> to lazy to add 128 to 20000 numbers or more. :) I COULD put the SJ> palette as low.. but then my other effects would all be in the high SJ> colors and that would be a pain. Write a procedure that does that after it reads them from disk. 20000 numbers would only take the computer a split second. --- EzyQwk V1.20 01fa018d * Origin: CSS Brisbane, Qld, Australia. (61-7-3367-3890) (3:640/350) --------------- FIDO MESSAGE AREA==> TOPIC: 107 PASCAL Ref: FA100011 Date: 05/19/98 From: JASEN BETTS Time: 05:45pm \/To: WIM KONING (Read 1 times) Subj: HOLD WK> JB> XXencode (many UUencode progs also do XXencode) check options. WK> WK> Ehmzz.. the encode program whose spread with SWAG!? I don't have that prog, it's easy to chage it to XXencode it you know how. bye. --- EzyQwk V1.20 01fa018d * Origin: CSS Brisbane, Qld, Australia. (61-7-3367-3890) (3:640/350) --------------- FIDO MESSAGE AREA==> TOPIC: 107 PASCAL Ref: FA100012 Date: 05/17/98 From: ELI GANAM Time: 07:20am \/To: HORST KRAEMER (Read 1 times) Subj: BP Hi Horst... >> Run-time error 105 is 'File not open for output' error, which can't be, >> sence you're not using files. HK> Test his program on your system: HK> begin HK> close(output); HK> writeln('hello') HK> end. So, how can he solve this problem? Will this work? Begin Assign (Output,''); Rewrite (Output); Writeln ('Hello!'); End. Eli Ganam. ... ??? ...? ,... ... , , --- ? * Origin: .O .O ,O ,O .O (2:407/303.3) --------------- FIDO MESSAGE AREA==> TOPIC: 107 PASCAL Ref: FA100013 Date: 05/20/98 From: DAVID CHORD Time: 01:37pm \/To: MIKE COPELAND (Read 1 times) Subj: Entering Passwords Mike Copeland wrote in a message to David Chord: DC> However, where is the problem with break, and how can you do a better DC> or as good as job without using it? MC> It's (quite) possible to not realize where the Break will "break MC> to", whether it'll skip other statements or exit from a whole code MC> block. One thing I am back in the habbit of doing is commenting END statements, like I might have : Procedure A_Procedure; begin If SomeByte = xx then Begin .. If Something = somethingelse then Begin .. If anotherthing = somethingelse then Begin End {if anotherthing = somethingelse} else begin end; {if anotherthing = somethingelse .. else} End; {If Something = somethingelse} End; {If SomeByte = xx} End; {A Procedure} I got into this habbit after going back to a program after some months, and found I had to insert some code in the right place in a screen that looked like : end; end; end; end; end; end; end; end; Finding the right place to insert the new code took a bit, as my indenting was not as it should be (which is why I also now use a Source Beautifier, to help me make sure my indenting is OK - saves time otherwise 'wasted' updating indentation when I alter large amounts of code - I want to get my thoughts/alterations down before I forget to much of what I am after). That of course makes figuring out where something like Break is going to jump to. MC> If one doesn't have a lot of experience and care with personal MC> style consistency (e.g. sloppy or spaghetti code), I don't think my code generally gets sloppy, and I didn't realise spaghetti code was possible with Pascal (Isn't that for line-numbered languages?) I suppose you either have structured code or spaghetti code? Normally my code is fairly structured.. MC> it's easy enough to miss what the compiler will actually execute or MC> assume that something will be executed which won't... Which is also part of why I step through new routines line by line once I have them ready to check, sometimes before I have them ready to check (if the blimmin thing will compile :-) MC> "Doing a better job without it"? That's awfully hard to state, MC> since such things are so style-dependant. Myself, I've never used MC> a Break or Continue (or GoTo) in Pascal, and I just _know_ I don't MC> need them to be a better Pascal programmer. But using them doesn't make anyone a worse programmer either :-) MC> They might be a _convenience_ to someone who doesn't know Pascal MC> well enough to use it as it was designed (and who's dependant on a MC> background of a non-structured, undisciplined language like COBOL, MC> BASIC, or even assembler), but once you learn and completely MC> accept Pascal for what it is and is intended to be, you'll never MC> use these things - because they're chances for errors/problems MC> which don't occur in the "native pascal" language. If I accepted Pascal for what it was 'intended to be' I wouldn't even be using it. It was attended to be a teaching aid. I accept it as a very good mid to high level language, and one that I can use fairly well. MC> These things were added to the 7.0 versions of TP/BP, I believe, MC> to make Pascal more attractive to programmers of other languages MC> Borland was trying to "steal away". Most experienced Pascal MC> programmers didn't want these additions, and very few use any of MC> them, as much as I have ever seen. I haven't yet used a continue, although I can see where it could be usefull, and I use Break from time to time, but only to increase execution speed most of the time, eg : While (Not Eof SomeFile) and (SomethingElse = False) Do Begin If Keypressed then begin {check for the abort key pressed, otherwise ignore} If Aborted then Break; End; {If Keypressed} [large routine that takes maybe 30-40 seconds to complete each pass] End; {While (Not EOF SomeFile) and (somethingElse = False) I suppose I could use 'If Not Aborted Then' before the start of the large routine, which achieves the same result. However, IME, that makes it a little harder to follow the flow/logic of the program, esp the keypress-test utine. DC> It's all very nice to teach someone that something is the ultimate DC> evil, but it does not make you a good teacher. In fact, if you don't DC> try to show them an alternative method or even give them clues and let DC> them learn by experience, you are virtually useless as a teacher, at DC> least in that regard. MC> Not at all. Many (of my former students) came into my Pascal MC> classes with (some) experience in other languages which needed such MC> things. Whereas I always tried to (re)teach these people the Pascal MC> (right) way of using the language, I always had some diehards who MC> insisted on using GoTos (all that was available at the time), I haven't used a GoTo in some years IIRC, but I can see their usefullness. If Iwas writing that program again from scratch, I'd probably use them again, I'd almost certainly use Break/Continue in there. MC> and I had to impose penalties on them to force them to understand MC> and use Pascal the right way. But it at least sounds like you were trying to teach them alternative methods to achieve the same result. MC> The fact is, _not_ using these unstructured constructs _is_ the MC> better way, but _proving_ it to some can only be done by letting MC> them make the mistakes over and over, falling farther and farther MC> behind as they take longer to "get it right", until they MC> eventually "get religion" and see what was originally MC> meant. Hardly easy to do, but sometimes the only way... I still disagree. My view on Goto is : It's not evil, it's sometimes usefull, but 99% of the time it should not be used. It has it's place, but touseit often is probably wrong (maybe someones writing something that lends itself well to GoTo). The programmers at Boorlandseem to be a fairly good group. I doubt they would have added something like GoTo if it was so bad. And yes, I do understand that with bad habbits, you sometimes need to let the person fall flat on their face a few times before you can help them learn to run. DC> Note that I do appreciate your efforts and what you have taught me or DC> made available to me and others over the last 5 years or so. But it DC> does annoy me a lot when someone with more experience says 'You can't DC> do that, it's the wrong way to do it and you'll have serious DC> problems!' then walks off without offering a hint of a better/correct DC> way of doing it. MC> Fair enough, but you've got to realize the limitations of this MC> medium, where I can't expend a lot of time or effort to explain MC> certain details, experiences, or factors which are behind things I MC> say. That I understand. However, 'That is bad' is no use to me. I'm not going to learn anything, I may loose a little or a lot of trust in you and in what you say, and will end up going to what I originally tried anyways because *I* know it works and I know how I can use it. 'That is bad, try this instead' is infinitely better, as I'll improve my programming skills and know a better way of doing things. Even a couple of keywords to lookup is so much betterthan nothing at all. MC> I've tried to do some of that here, but it's unreasonable to MC> think everyone will read all this dialog, or understand/believe it But often 'everyone else' isn't important. Someone comes with a specific problem, they're the ones who are the more important in the dialogue, they're the ones to really worry about. If you can show them a better way, they can show someone else a better way. If you don't show them a better way, youmight get thems ay to someone else you're trying to help 'that guy doesn'tknow what he'stalking about, here, use GoTo instead, works better'. At least give a hint of how to do it. MC> - sometimes it's best to say, "It's wrong, do it another way.", and MC> let the person try the different way (or not) and eventually find MC> out. I've been teaching people things for about 15 years now, even tho I am not quite 25 (another few weeks). I've only taught in any 'official' quality a couple of times, when I was 9 and was 'employed' by the school to help special-needs students (to also give me something to fillinmy time since Iwas so far ahead in most things), and once as a peer-tutor forthe local polytech when I was studying there (although I have been teaching people things from mechanics to farming ever since I was 9, and have been offered several jobs as a teacher/asst teacher (one school even offered to put me through Teachers Traning Colledge). Never have I ever come across a situation where it is a good idea to tell someone something is wrong without giving them a better alternative or at least an idea of an alternative. In many situations, it could cost someone their lives. Now, maybe computer programming isn't normally a life or death situation, but I strongly believethe principle still applies. The worst thing you can do is tell someone something is bad without giving an alternative. MC> Many of these concepts are subtle and experience-based, and not MC> something which can shown simply or caught with syntax checking. Maybe so, but if you give someone a place to start then they have a better chance of learning :-) Sorry for the long messages :-) Cya.. Dave Save your BBS! Join INTBBS_WK now! --- timEd 1.10 * Origin: GnomeVille MBBS 64-4 235-6887 (3:771/1560) --------------- FIDO MESSAGE AREA==> TOPIC: 107 PASCAL Ref: FA100014 Date: 05/20/98 From: DAVID CHORD Time: 02:17pm \/To: KIM FORWOOD (Read 1 times) Subj: help Kim Forwood wrote in a message to Paul Walker: PW> Hmm. I think I'll just stick at max., since you do more in memory PW> then. KF> I was only considering disk read/writes, so you're generally right KF> and a larger buffer will be better for a working with data in KF> memory. Hmm,how would you work that? Or do you mean say reading stuff from disk into a 32Kb buffer instead of an 8Kb bufer if you have 32Kb of data you want to process in one hit (instead of 4 smaller hits)? Cya.. Dave Save your BBS! Join INTBBS_WK now! --- timEd 1.10 * Origin: GnomeVille MBBS 64-4 235-6887 (3:771/1560) --------------- FIDO MESSAGE AREA==> TOPIC: 107 PASCAL Ref: FA100015 Date: 05/20/98 From: DAVID CHORD Time: 02:34pm \/To: PETER LOUWEN (Read 1 times) Subj: copy , plz help Peter Louwen wrote in a message to Koba Tsveniashvily: KT> I need to make a copy program so I wrote below code. KT> I compile it in HUGE memory model. PL> Look up farmalloc() in alloc.h. Will FarmAlloc() help me to get the famr I've always wanted? :-) :-) Dave Save your BBS! Join INTBBS_WK now! --- timEd 1.10 * Origin: GnomeVille MBBS 64-4 235-6887 (3:771/1560)