The java.util.zip package is part of the standard api and isn't too slow.lobster said:ive not seen any compression algorithms in java, it would be too slow.
this doesn't make sense and is irrelevant to the thread anywaycybotto said:I'm not a fan of Java, it has many flaws and is very static in developing terms. Not so much programming, keeping all that files/classes under control can be very challenging, setting them somewhere, getting them back again and always trying, catching and throwing, very odd
I'm not sure about java, but the delphi IDE and compiler is written in delphi. The same can be said for the C/C++ stuff. Java IDEs are generally written in java.cybotto said:In what Java is written? Can a language write it self?
no, the zip stuff in native to java. You're suffering from the misconception that java is inherently slow.With high propabilty that compression algorithm is written in C. Java only provides a higher level interface to it.
this doesn't make sense and is irrelevant to the thread anyway
cybotto said:IDEs are always written in that language which they represent, can you imagine a CEO from Pepsi has to use a vending machine from coca cola?
cybotto said:Java is slow, but chip in more processors, ram and viola. 4CPUs with 16GB of ram are standard and rock solid. Than it only looks like is fast.
cybotto said:It makes sense since there are different kind of programming styles, in PHP is possible to hack away and in a second see the result. In Java everything has to validated, compiled, or best after typing a dot looking which methods are available, writing helper classes etc.. It's not that efficient when you only want to keep going and play around. It's static since it is intended to be like this, to keep hackers out, it's just a different additude towards it. Some people like to think for hours and see their beautiful creation compiling and working and some just want to see as many permutations as possible in shortest time as possible.
For compiler designers, this is usually the Holy Grail ... to write the compiler in the language itself, and to compile it using the compiler. It's called 'bootstrapping' the compiler (as in 'to lift oneself up by one's bootstraps' - the verb 'boot' comes from the same phrase, is short for bootstrap).cybotto said:Can a language write it self?

Velouria said:to bootstrap it you do need to first write the compiler in another language
Then you expand it to include everything else (beyond input parsing, simple code generation and saving object code to a file): linking, optimisation, switcherama and so on.Velouria said:For compiler designers, this is usually the Holy Grail ... to write the compiler in the language itself, and to compile it using the compiler. It's called 'bootstrapping' the compiler (as in 'to lift oneself up by one's bootstraps' - the verb 'boot' comes from the same phrase, is short for bootstrap).
The GNU C Compiler can do this... and Tiny C can compile itself... dunno of other examples but there will be some.
Course the problem is, to bootstrap it you do need to first write the compiler in another language ... so it's a duplication of effort in a way, but a 'bootstrapped' compiler is regarded as being 'purer' if you get my drift![]()
No, it was Ken.laptop said:The ultimate Trojan Horse would be one inserted by the compiler. Can't remember who wrote the classic papers on this, but I'd not be surprised if it were Kernighan and/or Ritchie.
++++++++++[>+++++++>++++++++++>+++>+<<<<-]>++.>+.+++++++..+++.>++.<<+++++++++++++++.>.+++.------.--------.>+.>.

gurrier said:But it's not a programming language![]()
There are loads of reasons why learning to program with a microsoft product is a very bad idea. Not that their stuff is particularly terrible, just that when you want to learn to program, you want as much transparency as possible - the opposite of the microsoft coding philosophy.
Everybody knows that real coders learn to code with transistors anyway. If you can't construct an arbitrary Turing machine from J-K flip-flops, you're not worth it.![]()
Yep, using ILASM.EXE that really does compile and link..assembly extern mscorlib {}
.assembly hello {}
.method static public void main() cil managed
{ .entrypoint
.maxstack 1
ldstr "Hello world!"
call void [mscorlib]System.Console::WriteLine(class System.String)
ret
}

Stop pimping. Really.TAE said:If you are just starting out you may wish to learn a .net compatible language.
Eight is six too many. All you need is increment, and decrement-with-branchAs far as wacky languages are concerned, I like Brainfuck, a Turing-complete programming language consisting of only eight different commands.
TAE said:Personally I think "C++/CLI" is the best.
![]()
Lighten up. Really.rich! said:Stop pimping. Really.
Lol. Actually I started with C64 Basic and after a few months of frustration quickly moved to 6510 Assembler and then learned 68000 Assembler. Then I learned C.jæd said:Yes... This is the language I was taught most of the basic principles in. After C++ (and then C) I fould most other languages a breeze. Start of hard thnn get easier and that way you won't have any nasty suprises...
cybotto said:Academic concepts and good practise don't work well in real world anyway.
cybotto said:It makes sense since there are different kind of programming styles, in PHP is possible to hack away and in a second see the result. In Java everything has to validated, compiled, or best after typing a dot looking which methods are available, writing helper classes etc.. It's not that efficient when you only want to keep going and play around.
gnoriac said:I find with using Eclipse for writing Java I can get a program working relatively quickly because of Java's strong typing and Eclipse's hinting, whereas in PHP I have to spend ages hunting down the mistyped scalar names and array indexes.
boicy said:However there are topics that are of interest to both academia and industry. I would quote patterns or refactoring, Intentional Programming, Apect Orientated Programming and many more.

jæd said:Use an IDE to write PHP as well... Will avoid these problems and forces you to organise things in a more structured manner. Once I started using an IDE for Perl/Php/Python m productivity went up by 100%. As I've said... Professionals use IDEs. Dabblers use text editors.