Where should the type information be: in tags and descriptors 419
system's C.
That must have been fun as long as you avoided the alligators.
Right. :-). That's when my word, thingie, helps a lot when discussing aspects. If I said memory to a guy, his head would map in the electronics.
That pbuttactivating would have driven me nuts.
Heh heh ... giggle. There certainly are some potentially very serious issues as more and more "stuff" gets more and more connected. My current concerns run more toward...
I would have used the index of an encyclopedia as an example. Did you try this analogy? Its index has to be volume, then "memory address".
jmfbahciv) writes: A good suggestion. In fact, I'm in the process of reworking the programs in our system to convert existing binary files to ASCII...
representation
Yep. We spent weeks trying to design computing usage data using mixed mode. Then Larry Samberg, who was sitting on the floor, got this Far Away Look that developers get when their brains have swapped out from land of the living and are about to solve a huge problem. He asked why are we doing mixed mode; why can't we do ASCII then anybody can process the data...even TECO.
Programmers get confused again if you happen to use the names as a way to index into memory. I always traced this back to a person not understand the difference between a memory address and the contents of a memory address.
BAH
Subtract a hundred and four for e-mail.
Where should the type information be: in tags and descriptors 420
Alt Folklore Computers from Newsgroups
Where should the type information be: in tags and descriptors 418