 | | Re: Perl rules!
|
| (...) Relative pointers in the same segment take up half as much space as a 32 bit pointer. Depending on what you're doing, the savings here can be considerable. .COM programs used nothing but relative pointers and fit in less than 1 64K segment. (...) (25 years ago, 21-Jul-99, to lugnet.off-topic.geek)
| | | | | Re: Perl rules!
|
| (...) OK, relative-addressing mode is good. But it doesn't require segmented memory. All it requires is an instruction format with a defined result. For example, the conditional-jump instructions on the 6502 microprocessor[1] only used relative (...) (25 years ago, 22-Jul-99, to lugnet.off-topic.geek)
| | | | | Re: Perl rules!
|
| (...) Perhaps you're right, but that jump instruction is relative to the Instruction Pointer which uses a full register. The segmented way you are relative to a segment which only uses half a register. You can take advantage of this half register (...) (25 years ago, 22-Jul-99, to lugnet.off-topic.geek)
| | | | | Re: Perl rules!
|
| (...) OK, at this point I'll have to take your word for it. The segmented address still seems like a high price to pay for a half-register. (...) Maybe this is the case in LEdit -- I don't have knowledge of that source code. But in LDraw, the (...) (25 years ago, 22-Jul-99, to lugnet.off-topic.geek)
| | | | | Re: Perl rules!
|
| (...) That's a good suggestion. Especially because it's something I can make LDAO do. As opposed to some really nifty suggestions I've received which would require changing LDLite, or would be so processing-intensive that they aren't practical. (...) (25 years ago, 22-Jul-99, to lugnet.off-topic.geek, lugnet.cad.dev)
| | | | | Re: Perl rules!
|
| (...) I don't have source to LEdit either, but I used to write CAD software for a living around that time. We used all sorts of colormap manipulating tricks to speed up the rendering. These tricks just don't work in fixed color modes. You have to (...) (25 years ago, 22-Jul-99, to lugnet.off-topic.geek)
| |
