Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!mnetor!uunet!husc6!rutgers!sri-spam!ames!lll-lcc!lll-tis!ptsfa!hoptoad!academ!uhnix1!sugar!splut!jay From: jay@splut.UUCP (Jay Maynard) Newsgroups: comp.lang.c Subject: Re: *\"LDA\" ok? Message-ID: <92@splut.UUCP> Date: Tue, 25-Aug-87 05:55:28 EDT Article-I.D.: splut.92 Posted: Tue Aug 25 05:55:28 1987 Date-Received: Sat, 29-Aug-87 08:57:08 EDT References: <8877@brl-adm.ARPA> <8088@mimsy.UUCP> <87@splut.UUCP> <560@sugar.UUCP> Organization: Confederate Microsystems, League City, TX Lines: 32 Summary: Practical Pascals speak strings. In article <560@sugar.UUCP>, peter@sugar.UUCP (Peter da Silva) writes: > > Because most other languages, and all of the other languages that a > > programmer new to C is likely to know, handle strings intrinsically. > > Pascal doesn't even have a "variable length packed byte array" type. In > fact it *can't* have one unless you extend it. I know you love Turbo, > but it ain't Jensen & Wirth compatible. Turbo isn't the only Pascal that handles strings...in fact, how many strictly-J&W-compatible commercial Pascals do you know of? How many non-J&Ws? > As for your Volvo/68000 comment. What do *you* do on the 80x86 that > doesn't cause you to painfully code around segments? Use Turbo & never > go over 64K? I use linked lists allocated off the heap, where appropriate...or some similar technique. Generally, it can be dealt with through appropriate choice of algorithm (have we seen that discussion before...?) I've never done anything that required a single data element >64K, but such applications are fairly exotic. > -- Peter da Silva `-_-' ...!seismo!soma!uhnix1!sugar!peter > -- U <--- not a copyrighted cartoon :-> Yeah, I know...bleh. -- Jay Maynard, K5ZC...>splut!< | uucp: hoptoad!academ!uhnix1!nuchat!splut!jay "Don't ask ME about Unix... | (or sun!housun!nuchat) CI$: 71036,1603 I speak SNA!" | internet: beats me GEnie: JAYMAYNARD The opinions herein are shared by neither of my cats, much less anyone else.