Then use a null-terminated length. Or say that if the high bit of the length byte is one, ignore it and add the length from the next byte times 2*7, repeating as necessary.
Or if we have enough memory to worry about 64k strings (yes, we do, I'm not being sarcastic), let the size of the string be that of two or four longs, so it would tend to scale as computers get more powerful. 64-128 bits is plenty for 32-bit computers; 2^40 is already a terabyte, and using either C or Pascal strings for that large data gets timewise inefficient. And if the length is all ones (i.e., (unsigned)(-1)) count it as null-terminated. If you really had a string that large, you'd've rolled over on the next byte anyway.
Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:
Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.
Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.
All advertising materials mentioning features or use of this software must display the following acknowledgement: This product includes software developed by the University of California, Berkeley and its contributors.(This clause has since been removed.)
Neither the name of the University nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission.
Even better, give the kids password-protected access to an HTTP/DAV server and a computer to keep at home on loan for those who don't have one, and spend the first day of one class teaching those with recent OSes how to use built-in DAV capabilities (MS Web Folders and the like), and showing all how to use a custom web site hosted at the school to download/upload files (in case they can't use DAV per se). Nothing ventured back and forth, nothing lost.
Original poster was unclear with the terminology "C string". A C-string is not a string used in C. A C-string is a null-terminated string, or an ASCIIZ. The standard C-language string functions work with C-strings.
The Macintosh used to use Pascal-strings, even in C: the string "GPL" would be represented as {3, 'G', 'P', L'}, not {'G', 'P', 'L', 0}. This allows more efficient strlen() (and thus strcat(), strcpy() copying a few bytes at a time, etc.). Maybe Pascal strings should be used for security reasons; we've had enough problems with \0s in other locations, e.g., URLs. Pascal strings can represent all 256 unique bytes, not just 255.
However, I'm sure there's a reason C-strings are more popular now.
Get a group, fork these projects, and remarket them. No matter if we use exactly the same sources as the conventional version except for the logo files and the application name strings.
Anyone want to start the project? Or shall I, over the summer?
Ever wonder why the Harry Potter and Stuart Little movies used software called CinePaint, not by its former name of FilmGimp?
You trust the localizer and glideslope enough to land automatically? I'd be worried there'd be wind or the thing wouldn't be aligned or something...at most I'd use it while manually controlling, at the least I'd ignore it once I see the runway.
Of course, I've only used MS Flight Simulator, what do I know? (Other than crashing it is a lot cheaper....)
Actually, since Lindows/Lindash/Linspire/Let's Follow in Firefox's Footsteps is a Windows-like environment that uses Linux, the NetBSD (R) equivalent will probably be more like BSDows or something.
Except that looks like "BSD Ow's", or multiple BSD-related injuries.
You are not linking to the parent post. Slashdot is putting a link after your text. Therefore, you are not liable for linking to the parent post. If, however, I put my own link, then I would be liable.
You forgot an important part, which may have also gotten you past the lameness filter:
/*****
* DeDRMS.cs: DeDRMS 0.1
****
* Copyright (C) 2004 Jon Lech Johansen <jon-vl@nanocrew.net>
*
* This program is free software; you can redistribute it and/or modify
* it under the terms of the GNU General Public license as published by
* the Free Software Foundation; either version 2 of the License, or
* (at your option) any later version.
*
* This program is distributed in the hope that it will be useful,
* but WITHOUT ANY WARRANTY; without even the implied warranty of
* MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
* GNU General Public License for more details.
*
* You should have received a copy of the GNU General Public License
* along with this program; if not, write to the Free Software
* Foundation, Inc., 59 Temple Place - Suite 330, Boston, MA 02111, USA.
****/
Actually, this->function() is redundant in a member function, and invalid elsewhere. You only use this if you actually need a pointer, a reference, or a copy of the current object, such as:
assert(this) might be helpful, in case you're running a member function on a null pointer (!?). assert(dupe) will return either true or operator bool(dupe), since dupe is an object, not a pointer. What you probably meant is:
Copyright infringement is not a "right", let alone a right that we might have. You will never see this capitalist country condone copyright infringement on the scale the warez groups produce.
This is offtopic (mod me down, karma-bonus isn't working anyway), but I'll bite:
What do you have to look forward to? Following in their footsteps: creating a wildly successful capitalist business that uses others' open-source to reduce costs, in the process possibly contributing back in minor amounts. It worked for Apple, it worked for Google, it worked for countless others I won't bother to name, it'll work for me.
Make a P2P app that runs over HTTPS, so that the connection looks plausible and the decryption is nontrivial and maybe DMCAable...or better yet, one that runs over e-mail with message-level encryption and chunking (for largish files), since mail works reasonably quickly and most home users use e-mail. Records of P2P apps would drown in the records of legit applications.
If the law is unjust, fight it. Don't break it and hide; that's morally wrong and cowardly. Get the lawmakers to change the law, or break the law and take the penalty.
Seriously, especially on direct connections or LANs - or even within the same ISP - cabling is so high quality and routers are fast enough that UDP suffices. I'm not sure if it's likely to get my data to Namibia via Belgium, but for most purposes UDP with a lightweight correction protocol ("I didn't get packet 45 of the set in 2 seconds, can you send it again?") and possibly parity or error correction would be enough, without the several layers of TCP acknowledgements.
Re:This is not just for laughs
on
SimChurch
·
· Score: 1
Do you not think there was similar outcry at the first TV broadcast services? TV probably wasn't that popular, and receiving a good broadcast may have been only marginally more common than broadband today.
We're seeing the typical resistance to technology...wait and see if it has merit (which it might have, if the online church becomes too much online and too little church).
Slashdot Mirror
nuclear disasters visit YOU!
I'm a bit worried about the .2 people
They're in Chernobyl. What did you expect, non-mutants?
Then use a null-terminated length. Or say that if the high bit of the length byte is one, ignore it and add the length from the next byte times 2*7, repeating as necessary.
Or if we have enough memory to worry about 64k strings (yes, we do, I'm not being sarcastic), let the size of the string be that of two or four longs, so it would tend to scale as computers get more powerful. 64-128 bits is plenty for 32-bit computers; 2^40 is already a terabyte, and using either C or Pascal strings for that large data gets timewise inefficient. And if the length is all ones (i.e., (unsigned)(-1)) count it as null-terminated. If you really had a string that large, you'd've rolled over on the next byte anyway.
Uh...wrong BSD license. The original license was:
Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:
THIS SOFTWARE.... (cue disclaimers)
Even better, give the kids password-protected access to an HTTP/DAV server and a computer to keep at home on loan for those who don't have one, and spend the first day of one class teaching those with recent OSes how to use built-in DAV capabilities (MS Web Folders and the like), and showing all how to use a custom web site hosted at the school to download/upload files (in case they can't use DAV per se). Nothing ventured back and forth, nothing lost.
And your chosen culture/nation/whatever's history is immaculate of crime?
Original poster was unclear with the terminology "C string". A C-string is not a string used in C. A C-string is a null-terminated string, or an ASCIIZ. The standard C-language string functions work with C-strings.
The Macintosh used to use Pascal-strings, even in C: the string "GPL" would be represented as {3, 'G', 'P', L'}, not {'G', 'P', 'L', 0}. This allows more efficient strlen() (and thus strcat(), strcpy() copying a few bytes at a time, etc.). Maybe Pascal strings should be used for security reasons; we've had enough problems with \0s in other locations, e.g., URLs. Pascal strings can represent all 256 unique bytes, not just 255.
However, I'm sure there's a reason C-strings are more popular now.
then tell me who here has used DeCSS. Not software that claims to use DeCSS, DeCSS in the stand-alone, propagated form. Or DeDRMS, for that matter.
Code can be faked, there is no proof until it is run. Have you run it?
Yes, let's all taunt the researchers who're looking for Noah's ark while still trying to build an OS and environment that can compete with Microsoft.
If we can hold our idealistic beliefs, let them do the same.
Get a group, fork these projects, and remarket them. No matter if we use exactly the same sources as the conventional version except for the logo files and the application name strings.
Anyone want to start the project? Or shall I, over the summer?
Ever wonder why the Harry Potter and Stuart Little movies used software called CinePaint, not by its former name of FilmGimp?
You trust the localizer and glideslope enough to land automatically? I'd be worried there'd be wind or the thing wouldn't be aligned or something...at most I'd use it while manually controlling, at the least I'd ignore it once I see the runway.
Of course, I've only used MS Flight Simulator, what do I know? (Other than crashing it is a lot cheaper....)
Actually, since Lindows/Lindash/Linspire/Let's Follow in Firefox's Footsteps is a Windows-like environment that uses Linux, the NetBSD (R) equivalent will probably be more like BSDows or something.
Except that looks like "BSD Ow's", or multiple BSD-related injuries.
(Yes, an apostrophe there is correct)
You are not linking to the parent post. Slashdot is putting a link after your text. Therefore, you are not liable for linking to the parent post. If, however, I put my own link, then I would be liable.
For those of you who don't have VS.NET but do have Windows, Microsoft's own compilers without the IDE are free (though of course not Free).
.NET SDK 1.1
MS
What good is code if you can't compile it? I get the feeling that most of you who are passing the code will never use it....
Copyright infringement is not a "right", let alone a right that we might have. You will never see this capitalist country condone copyright infringement on the scale the warez groups produce.
This is offtopic (mod me down, karma-bonus isn't working anyway), but I'll bite:
What do you have to look forward to?
Following in their footsteps: creating a wildly successful capitalist business that uses others' open-source to reduce costs, in the process possibly contributing back in minor amounts. It worked for Apple, it worked for Google, it worked for countless others I won't bother to name, it'll work for me.
Make a P2P app that runs over HTTPS, so that the connection looks plausible and the decryption is nontrivial and maybe DMCAable...or better yet, one that runs over e-mail with message-level encryption and chunking (for largish files), since mail works reasonably quickly and most home users use e-mail. Records of P2P apps would drown in the records of legit applications.
If the law is unjust, fight it. Don't break it and hide; that's morally wrong and cowardly. Get the lawmakers to change the law, or break the law and take the penalty.
In Soviet Russia, Sex sues YOU!
Yahoo! News confirms: BGP connections ARE DYING!
--
In Soviet Russia, the Internet attacks you!
--
I'm directly connected to every computer; I don't use routing tables, you insensitive clod!
(the last one was admittedly a bit contrived.)
Seriously, especially on direct connections or LANs - or even within the same ISP - cabling is so high quality and routers are fast enough that UDP suffices. I'm not sure if it's likely to get my data to Namibia via Belgium, but for most purposes UDP with a lightweight correction protocol ("I didn't get packet 45 of the set in 2 seconds, can you send it again?") and possibly parity or error correction would be enough, without the several layers of TCP acknowledgements.
Do you not think there was similar outcry at the first TV broadcast services? TV probably wasn't that popular, and receiving a good broadcast may have been only marginally more common than broadband today.
We're seeing the typical resistance to technology...wait and see if it has merit (which it might have, if the online church becomes too much online and too little church).