This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
Messages - calcdude84se
Pages: 1 ... 102 103 [104] 105 106 ... 161
1546
« on: July 27, 2010, 04:13:20 pm »
So, quick tutorial on Port. (And the link port in general) As you know, the link port has two lines on which to send data, the tip and the ring. Each can be in one of two states, high or low. When you write a set bit, it pulls that line low, while writing a reset bit allow it to go high. Bit 0 is the tip and bit 1 is the ring. Like Quigibo said, you write 0 to let both go high, 1 to pull the tip low and let the ring go high, 2 to let the tip go high and pull the ring low, and 3 to pull both low. Reading, however, is somewhat different. Instead of a set bit indicating that it is low, a set bit indicates that the line is high. A reset bit indicates that the line is low. This means that when you read 0, both are low; 1, the tip is high and the ring is low; 2, the ring is high and the tip is low; 3, both are high. With respect to two connected calcs, a line is read as low if either calc is pulling it low. The line will only be read as high if both calcs are letting it go high. Hope this helps! 
1547
« on: July 27, 2010, 03:59:43 pm »
Qazz, it only messes up what's displayed, it doesn't crash. Putting such features could be difficult because Disp A could actually be useful. Not much can be done there  As for using labels literally, yeah, it probably should be reserved as an "advanced use." The suggestions I've given (definitely "address-of" and less likely advanced operations for "files" (or what I'm calling extended pointers)) probably don't need to be given any "advanced" label, though. I agree a keyhook to compile would be nice. 
1548
« on: July 27, 2010, 12:10:42 am »
Speaking it is definitely the hardest part of any language, but is definitely an essential component of fluency. (Unless it's a classical language (e.g. Latin) (Unless you're like me  ))
1549
« on: July 26, 2010, 11:52:47 pm »
I voted for the first one because the well-known ones are, well, well-known. IMO it should be mainly to showcase or at least present the lesser-known ones. Just my two cents
1550
« on: July 26, 2010, 11:16:47 pm »
So I've been a little curious about this for a while now. What programming human languages does everyone know? How skilled are you at them? (Like beginner, intermediate, advanced.) I shall start: TI-BASIC: Beginner-IntermediateEnglish: Advanced Latin: Intermediate-Advanced Italian: Beginner (I need more time...) Lojban: Beginner (I was bored, okay? ) This happens to be a shameless rip-off of the Programming Languages topic, in case you haven't noticed
1551
« on: July 26, 2010, 10:59:00 pm »
We as a community have way too much time on our hands
1552
« on: July 26, 2010, 10:54:24 pm »
Oh boy... TI-BASIC: Intermediate-Advanced z80 ASM: Intermediate-Advanced C: Intermediate-Advanced Java: Intermediate-Advanced C++: Beginner-Intermediate Python: Intermediate Perl: Beginner-Intermediate Javascript: Intermediate Haskell: Beginner-Intermediate HTML/CSS: Beginner-Intermediate Axe: Intermediate-Advanced If I can think of more I'll edit my post Edit: Oops I forgot Axe.
1553
« on: July 26, 2010, 06:58:27 pm »
Also, bug I meant to report earlier. I have to pass 7 as the size argument to GetCalc( for real variables else I get memory leaks (too high) or crashes (too low). I guess this isn't a bug, but you should document it
1554
« on: July 26, 2010, 06:49:25 pm »
That. Sounds. Awesome! Excellent work! Hm... compression techniques... At any rate, excellent. Should've done a different song, though
1555
« on: July 26, 2010, 05:56:32 pm »
Quigibo, do you mind explaining the floating-point format to us?
nemo, the main problem is that floating-point numbers use a very different format than two-byte integers.
1556
« on: July 26, 2010, 05:00:09 pm »
Of course, it's still more optimized to do "Str1->Str1 and use Str1 multiple times than using "Str1" multiple times, since each occurrence of "Str1" adds size to the program, while assiging it to a pointer just does it once.
I think the intended use was with text and other data that would only need to be used one time.
1557
« on: July 26, 2010, 04:57:23 pm »
Mine takes three nibbles, while his takes one byte, or two nibbles. It's only 50% larger Not to mention I'm assuming the 'F' tile won't be used as often. * calcdude goes off to code this
1558
« on: July 26, 2010, 04:51:28 pm »
Because normally Str1 is, well, a pointer. But it always points to data contained w/in the program.
Also, with 0.4.0, you can inline the text like 'GetCalc("Str1",16)->A'
1559
« on: July 26, 2010, 04:47:55 pm »
Nice. However, I think I should tell you that RLE is typically done slightly differently, with a reserved number to indicate runs. For example:
.Uncompressed (each tile is a half-byte)
[567222220874999F
[033AAAAAAAAAAAAA
[AAA23279BBBBB8FF
.24 bytes
.Compressed
[567F520874999F1F
[033F0A23279F5B8F
[2F
.17 bytesWhere normal data is just inserted, and a run (more than three here) is indicated by 'F' followed by the run length (one nibble, 0 is length 16) followed by the tile number. An 'F' tile is always recorded in run format because it would otherwise be treated as the start of a run.
I'll try to get some code up in a bit.
1560
« on: July 26, 2010, 04:35:44 pm »
No, but you can upgrade The ability to use values directly rather than storing them to pointers first was added with version 0.4.0
Pages: 1 ... 102 103 [104] 105 106 ... 161
|
Show Posts