| TIP: Click on subject to list as thread! | ANSI |
| echo: | |
|---|---|
| to: | |
| from: | |
| date: | |
| subject: | Re: Pascal strings |
So to david nugent do I speak these words: Friday October 08 1993 18:29, david nugent wrote to Steven Pasztor: >> Which would be most likely to be usefull, adding TP string >> support to C++, and using it to drive the ASM routines, or >> converting the ASM routines to handle C++? dn> No idea - it depends on whetther TP strings are worth supporting for dn> whatever you're using it for. But a simple "TP" string translation to C++ dn> won't quite work - and besides, you'll loose out on the better dn> optimisations possible in C++, such as length > 255, reference counting dn> and flexible/efficient use of memory. Syntactically, they can be designed dn> to be used pretty much the same as TP strings, but a C++ implementation dn> will usually be the more efficient. So I take the easyer option, and rewrite the ASM routines! :-) The length rarely bothers me, besides, you still have to specify the length don't you? And it's very rare that I use a full TP string. As for the use of memory, how would they differ? Wouldn't they both be treated as an array of characters? nevets ... A crate of UZI's, a carton of whiskey...lets go to Disneyland! --- FMail 0.94* Origin: HELP!!! (3:632/103.123) SEEN-BY: 50/99 54/54 99 620/243 622/405 623/630 632/103 301 348 365 386 998 SEEN-BY: 633/371 634/383 384 635/502 503 544 555 570 636/100 670/206 711/401 SEEN-BY: 711/409 430 807 808 809 932 934 712/623 627 713/888 714/906 800/1 @PATH: 632/103 348 635/503 50/99 54/54 99 711/808 809 934 |
|
| SOURCE: echomail via fidonet.ozzmosis.com | |
Email questions or comments to sysop@ipingthereforeiam.com
All parts of this website painstakingly hand-crafted in the U.S.A.!
IPTIA BBS/MUD/Terminal/Game Server List, © 2025 IPTIA Consulting™.