|
|
| Author |
Message |
virl
|
|
.
| 
May 19 03:23 UTC 1994 |
well anybody know anything about Clippers???
hi
|
| 14 responses total. |
kentn
|
|
response 1 of 14:
|
May 19 03:52 UTC 1994 |
Like the kind for cutting hair?
|
rcurl
|
|
response 2 of 14:
|
May 19 05:11 UTC 1994 |
The ships are nice.
|
kentn
|
|
response 3 of 14:
|
May 19 05:26 UTC 1994 |
Oh, yeah, forgot about those. They're wonderful.
|
davel
|
|
response 4 of 14:
|
May 19 12:22 UTC 1994 |
Make sure they're made from the best grade of tool steel.
|
rcurl
|
|
response 5 of 14:
|
May 19 13:53 UTC 1994 |
Nail clippers. That's what I was trying to think of. Thanks, davel.
|
davel
|
|
response 6 of 14:
|
May 19 15:52 UTC 1994 |
Yeah, they get dull after a while & tear the nails instead of clipping.
|
remmers
|
|
response 7 of 14:
|
May 20 12:32 UTC 1994 |
#0 isn't real clear, but maybe he's asking about the clipper chip?
|
davel
|
|
response 8 of 14:
|
May 20 17:29 UTC 1994 |
or the xbase product?
|
rcurl
|
|
response 9 of 14:
|
Feb 6 16:03 UTC 1995 |
This seems like a good "miscellaneous" item to ask a couple of passing
questions (trusting that no everyone has done a forget on such a short
item):
1. I downloaded a <file>.sit.hqx, and after decoding and expanding, I
found it was a *disk image*. So I had to run that and load it to a disk.
What it created was another .sit file on the disk! (A big one - 1.3 MB)
That when expanded (to the desktop, of course) was finally a useable file
(actually, a folder of many files). Can anyone think of why it was done
that way, instead of having the final .sit file itself archived?
2. What does the following expression mean: "A C++ Class that
parses and constructs almost all of...." (a variety of data formats)?
It was a .zip file that I downloaded and when expanded became a
large number of small files that appeared to be code (presumably
C++?) for use on windows, most of which had the extensions .CPP
or .HPP (and a few .MAK). I know what the codes are supposed to
do (when, presumably, compiled) - read data formats - but I'd like
some clarification of "A C++ Class", and whether those extensions
are something standard. (I don't "do windows".)
|
srw
|
|
response 10 of 14:
|
Feb 7 01:36 UTC 1995 |
Someone stuffed those folders so they would fit on a disk. Then they made an
image file of the disk. Why they wanted that rather than the file itself I
do not know. Disk Images are often used to release software, though.
Stuffing the final disk image was just plain dumb.
It was a waste of time and effort. It was probably done in ignorance.
A "class" is an element of an object oriented language, and C++ is an
example of such a language. A C++ class is a data type which specifies
a certain kind (class) of object. It is more than a data type, as it
contains "methods" which are the oop variant of subroutines.
So a class is like a reusable program fragment in an oop.
What you have is objected oriented source code.
|
rcurl
|
|
response 11 of 14:
|
Feb 7 06:53 UTC 1995 |
Thanks, Steve. "Learn something new every day.", they say: sure do. In
regard to 1, I can't believe the author did that "in ignorance". The files
are data and map resources for an enormous GIS application that links WX,
GPS, packet ham radio, and lots more, and is a national standard. I guess
that one stays a mystery until I meet a APRS guru.
|
kentn
|
|
response 12 of 14:
|
Feb 7 17:24 UTC 1995 |
I believe the ignorance theory. I really like it when I see (for
example) an archive compression program compressed via the same
archive compression method (how do I uncompress it? Catch-22, you'd
figure people could understand that). Some people get so hung up
on compressing things that they go overboard. It's easy to believe
ignorance...
|
srw
|
|
response 13 of 14:
|
Feb 8 07:14 UTC 1995 |
In fairness, sometimes compressions programs are provided in that format
for those that have earlier versions. Still, auto-expanding versions should be
available.
In Rane's case we have a file compressed, then wrapped in something rather
trivial, then an attempt was made to compress it again with the same
compression algorithm. I'll bet the last step was a waste of time and effort.
|
rcurl
|
|
response 14 of 14:
|
Feb 8 16:13 UTC 1995 |
It might be a vestige from an earlier version where the (expanded) files
were created on a floppy, so just selected ones could be copied to the
desktop - and then the folder got too large, so it was compressed so it
would fit on the floppy. I can't think of a reason, though, why the disk
image step has been left, with systems having more RAM.
|