Could someone explain how this is suppoused to work: * when the copyright expires it's allowed to copy the work in question * but assum the work is on a copy protected media like a dvd * acording to the DMCA it's then still ilegal to use copy protection cracking software
- so how are we legaly sopoused to be able to copy a copy protected work even when the copyright has expired ?
Sorry I messed up my first post, this should be more readable.
Having worked on large scale systems for a few years I would say that the following properties are usefull for a language to have:
* simple syntax (especialy important if your using a non-standard language)
* the language should have a good expresive power, e.g. in the language (Erlang) i use regulary there would only be a need for three rather than your five constucts, recursion would be used for the loops (Do while, Do until), the conditionals (If then Else, Case) would be replaced by a pattern matching (multi choice branching).
(I'm not sure what you mean by Simple sequence)
* error messages during compile and runtime should be expresive i.e. the reason of failure should be easy to understand and the location (on which line is the error introduced) of the error should be easy to pinpoint - Virtual Machines are usally pretty good at this (in the runtime case, e.g. C vs Java crashes)
* easy to use and reasonably compleat set of support libaries
* no pointers, garbage collection - reduces bugs
* modularity - functionalty is divided into modules or classes (depends on if your using functional or OO languages)
* code loading (onto a running system) support - this is usefull in many ways, the customer might need this if they are running things like phone systems or servers that should never be down (max downtime = a few hours a year), interactive enviroments - compile module - load module - test if bug fix worked (some test enviroments take to much time to restart for the normal test - fix bug - compile - test cycel)
- or to sum it up correctness and development speed are the two most important aspects when developing software.
Having worked on large scale systems for a few years I would say that the following properties are usefull for a language to have:
* simple syntax (especialy important if your using a non-standard language)
* the language should have a good expresive power, e.g. in the language (Erlang) i use regulary there would only be a need for three rather than your five constucts, recursion would be used for the loops (Do while, Do until), the conditionals (If then Else, Case) would be replaced by a pattern matching (multi choice branching).
(I'm not sure what you mean by Simple sequence)
* error messages during compile and runtime should be expresive i.e. the reason of failure should be easy to understand and the location (on which line is the error introduced) of the error should be easy to pinpoint - Virtual Machines are usally pretty good at this (in the runtime case, e.g. C vs Java crashes)
* easy to use and reasonably compleat set of support libaries
* no pointers, garbage collection - reduces bugs
* modularity - functionalty is divided into modules or classes (depends on if your using functional or OO languages)
* code loading (onto a running system) support - this is usefull in many ways, the customer might need this if they are running things like phone systems or servers that should never be down (max downtime = a few hours a year), interactive enviroments - compile module - load module - test if bug fix worked (some test enviroments take to much time to restart for the normal test - fix bug - compile - test cycel)
- or to sum it up correctness and development speed are the two most important aspects when developing software.
Slashdot Mirror
Could someone explain how this is suppoused to work:
* when the copyright expires it's allowed to copy the work in question
* but assum the work is on a copy protected media like a dvd
* acording to the DMCA it's then still ilegal to use copy protection cracking software
- so how are we legaly sopoused to be able to copy a copy protected work even when the copyright has expired ?
Sorry I messed up my first post, this should be more readable.
Having worked on large scale systems for a few years I would say that the following properties are usefull for a language to have:
* simple syntax (especialy important if your using a non-standard language)
* the language should have a good expresive power, e.g. in the language (Erlang) i use regulary there would only be a need for three rather than your five constucts, recursion would be used for the loops (Do while, Do until), the conditionals (If then Else, Case) would be replaced by a pattern matching (multi choice branching).
(I'm not sure what you mean by Simple sequence)
* error messages during compile and runtime should be expresive i.e. the reason of failure should be easy to understand and the location (on which line is the error introduced) of the error should be easy to pinpoint - Virtual Machines are usally pretty good at this (in the runtime case, e.g. C vs Java crashes)
* easy to use and reasonably compleat set of support libaries
* no pointers, garbage collection - reduces bugs
* modularity - functionalty is divided into modules or classes (depends on if your using functional or OO languages)
* code loading (onto a running system) support - this is usefull in many ways, the customer might need this if they are running things like phone systems or servers that should never be down (max downtime = a few hours a year), interactive enviroments - compile module - load module - test if bug fix worked (some test enviroments take to much time to restart for the normal test - fix bug - compile - test cycel)
- or to sum it up correctness and development speed are the two most important aspects when developing software.
Having worked on large scale systems for a few years I would say that the following properties are usefull for a language to have: * simple syntax (especialy important if your using a non-standard language) * the language should have a good expresive power, e.g. in the language (Erlang) i use regulary there would only be a need for three rather than your five constucts, recursion would be used for the loops (Do while, Do until), the conditionals (If then Else, Case) would be replaced by a pattern matching (multi choice branching). (I'm not sure what you mean by Simple sequence) * error messages during compile and runtime should be expresive i.e. the reason of failure should be easy to understand and the location (on which line is the error introduced) of the error should be easy to pinpoint - Virtual Machines are usally pretty good at this (in the runtime case, e.g. C vs Java crashes) * easy to use and reasonably compleat set of support libaries * no pointers, garbage collection - reduces bugs * modularity - functionalty is divided into modules or classes (depends on if your using functional or OO languages) * code loading (onto a running system) support - this is usefull in many ways, the customer might need this if they are running things like phone systems or servers that should never be down (max downtime = a few hours a year), interactive enviroments - compile module - load module - test if bug fix worked (some test enviroments take to much time to restart for the normal test - fix bug - compile - test cycel) - or to sum it up correctness and development speed are the two most important aspects when developing software.