Your rights may be stolen either way. Would you have the funds to defend an open source license in court if some disrespectful company forks the code and claims it as their own ?
Have you decided on an open source license yet ? It appears as though you'd like to retain the sole rights to publish the non-electronic version of the game. Would you allow a fork that allowed printing of the board/cards/whatever else ?
I was considering buying Vista on the release date. A one-off cost for 5 years of use doesn't seem to bad.
I was having a "I hate Microsoft week" a while back when the new Vista EULA's were released (what ? documentation for Visual Studio costs extra ? What a joke!). I've replaced motherboards about 4/5 times in the past 5 years. There is no way I am going to purchase the same product 2 or 3 times.
I've now moved to Ubuntu, and will be recommending Ubuntu to family and friends. It's easy to install, easy to use, and free in every sense of the word.
So you're going to recommend in a paper that people not use locks, despite there being no alternative ? I doubt that insurance companies would recommend this action.
Perhaps your paper needs more work if you plan on stating that ?
Plus, without ever using Sybase (I'm more of a PostgreSQL fan), I'm fairly sure that Sybase would provide a C/C++ api.
(For those that haven't caught on, Sybase is a competitor to such products as Oracle, DB2, PostgreSQL etc, and is not compareable to silly little toys such as MS Access)
I realise the parent was troll bait, but I'll reply anyway...
In the *nix world:
// Writing to memory: int a = 5; // Or, in case you don't think the stack counts as a "block of memory": int *b = new int; *b = 5;
Writing to a disk:
open, check for EINTR and repeat.
write, repeat until everything is written, repeat on EINTR, do something on an error
close, and check to ensure the data previously written didn't cause an error (eg. If it was over NFS)
So, I seriously doubt you could argue that writing to a file is the way forward. Conversely, many people will mmap a file so that it looks like a block of memory, and in many cases this can reduce complexity. Being able to use an iterator pattern over the file data is priceless.
Assigning whether the "file" should contain persistent data or transient 'buffer' data would increase complexity.
btw, what happens when the so called "disk cache controller" decides that the disk is full ?
So you're willing to argue that the article refers to " IEEE 1394 or USB powered computer light " ?
Patent No. 6,757,593 (" Vehicle expression operation control system, vehicle communication system, and vehicle which performs expression operation") appears to be a more appropriate fit.
Not sure what article you were reading, but I pulled that quote from the/. linked story.
I was reading the information posted on/., which was nice enough to include a link to the correct patent:
The NY Times/IHT reports that four inventors working for Toyota in Japan have won a patent
On previous installations of various Linux distros, the first step I've taken is to download the various patches and updates. Same procedure with Windows.
Linux isn't a magic silver bullet that will solve all of your security problems.
"permissions embedded in the file system" is always overcome by people using the magic chmod 777 fix. "Real users" is useless if all the important personal data is stored by the user using the web browser.
I'm typing this using Firefox 0.9 under XP. I don't particularly like Windows, but there are other people who need to use this machine. For the many millions of people using Windows, using software other than IE/OE is a great choice.
My uni basically only taught Java as a programming language, which proved (not very) useful for my first real development job in c++.
Things I wished I'd realised sooner: 1) Learn how to use (or write, if you're brave) STL iterators with containers. 2) Learn the difference between the stack and the heap. 3) Use memory leak checkers (eg. valgrind), as you WILL get memory management incorrect. 4) Realise that destructors in c++ are actually useful, in that you know (more or less) when they'll be run.
I've read some code written by people claiming to know c++ with a java background. Every single object was created with the new object, including those used only in the current scope. yeeech.
Sounds like just the thing for testing a newly compiled kernel without modifying the bootloader.
I'd much prefer to test the kernel on the "real" system then some sort of virtualisation (VMware etc) using kexec. Much faster than accidentally screwing the system, trying to find a bootable cd etc.
The world doesn't need more scientists believing they can code.
Software development requires -engineers-, not scientists. All the math/physics theory in the world won't teach you to write scalable, maintainable, reusable software.
So, unless you're planning on staying in a research field for the rest of your career, you'd better learn how to code properly.
Slashdot Mirror
Perhaps your hard drives are overheating ? Installing a fan may help :p
Your rights may be stolen either way. Would you have the funds to defend an open source license in court if some disrespectful company forks the code and claims it as their own ?
Have you decided on an open source license yet ? It appears as though you'd like to retain the sole rights to publish the non-electronic version of the game. Would you allow a fork that allowed printing of the board/cards/whatever else ?
Why would you be unwilling to provide a set of rules to a company who hasn't signed an NDA, yet wish to create a FOSS version ?
Either you wish the game to be open, or you don't. Choose one.
I was considering buying Vista on the release date. A one-off cost for 5 years of use doesn't seem to bad.
I was having a "I hate Microsoft week" a while back when the new Vista EULA's were released (what ? documentation for Visual Studio costs extra ? What a joke!). I've replaced motherboards about 4/5 times in the past 5 years. There is no way I am going to purchase the same product 2 or 3 times.
I've now moved to Ubuntu, and will be recommending Ubuntu to family and friends. It's easy to install, easy to use, and free in every sense of the word.
Where's the Vision in this Proposal?
I think the point of the proposal is that you'll need an approved DRM device before watching the vision.
So you're going to recommend in a paper that people not use locks, despite there being no alternative ? I doubt that insurance companies would recommend this action.
Perhaps your paper needs more work if you plan on stating that ?
-
Python
-
Perl
-
JDBC
Plus, without ever using Sybase (I'm more of a PostgreSQL fan), I'm fairly sure that Sybase would provide a C/C++ api.(For those that haven't caught on, Sybase is a competitor to such products as Oracle, DB2, PostgreSQL etc, and is not compareable to silly little toys such as MS Access)
TCP/IP is designed for reliability.
Writing to a disk:
- open, check for EINTR and repeat.
- write, repeat until everything is written, repeat on EINTR, do something on an error
- close, and check to ensure the data previously written didn't cause an error (eg. If it was over NFS)
So, I seriously doubt you could argue that writing to a file is the way forward. Conversely, many people will mmap a file so that it looks like a block of memory, and in many cases this can reduce complexity. Being able to use an iterator pattern over the file data is priceless.Assigning whether the "file" should contain persistent data or transient 'buffer' data would increase complexity.
btw, what happens when the so called "disk cache controller" decides that the disk is full ?
Wouldn't it have been easier to just take the phone with you ? Surely, that's why they're designed small enough to fit in your hand ?
/.
Oh, yeah, I forgot this was
Patent No. 6,757,593 (" Vehicle expression operation control system, vehicle communication system, and vehicle which performs expression operation") appears to be a more appropriate fit.
I was reading the information posted on
You've messed up the patent number slightly. The article refers to patent # 6,757,593
Yet another sheep without a clue.
On previous installations of various Linux distros, the first step I've taken is to download the various patches and updates. Same procedure with Windows.
Linux isn't a magic silver bullet that will solve all of your security problems.
"permissions embedded in the file system" is always overcome by people using the magic chmod 777 fix. "Real users" is useless if all the important personal data is stored by the user using the web browser.
I'm typing this using Firefox 0.9 under XP. I don't particularly like Windows, but there are other people who need to use this machine. For the many millions of people using Windows, using software other than IE/OE is a great choice.
My uni basically only taught Java as a programming language, which proved (not very) useful for my first real development job in c++.
Things I wished I'd realised sooner:
1) Learn how to use (or write, if you're brave) STL iterators with containers.
2) Learn the difference between the stack and the heap.
3) Use memory leak checkers (eg. valgrind), as you WILL get memory management incorrect.
4) Realise that destructors in c++ are actually useful, in that you know (more or less) when they'll be run.
I've read some code written by people claiming to know c++ with a java background. Every single object was created with the new object, including those used only in the current scope. yeeech.
Estonia hey...
that's an aweful lot of pringles cans I'm gonna need for free net.
Sounds like just the thing for testing a newly compiled kernel without modifying the bootloader. I'd much prefer to test the kernel on the "real" system then some sort of virtualisation (VMware etc) using kexec. Much faster than accidentally screwing the system, trying to find a bootable cd etc.
The world doesn't need more scientists believing they can code. Software development requires -engineers-, not scientists. All the math/physics theory in the world won't teach you to write scalable, maintainable, reusable software. So, unless you're planning on staying in a research field for the rest of your career, you'd better learn how to code properly.