There is a saying that "you can write FORTRAN in any language" and this appears to be a practical embodiment of this. It is a good article from a technical point of view though.
What the author really desires is the equivalent of a C compiler for the .NET platform (C.NET perhaps) but on the Java platform that is available to him. He could implement a full bytecode compiler for an arbitrary language (similar to JYthon) but has pragmatically decided it is easier to implement it this way.
That said I would agree with the other posters that it is an entirely wrong-headed thing to do. It is better to learn the new String class than keep using an old API. A good programmer should be able to switch languages in less time than it would take to write such a library.
Yes, absolutely: I write Fortran in any language as I really like Fortran. Thank you for positive evaluation of technical level of the article. But I must say that the article is intended not for Java programmers but for MPU-programmers who are very specific persons: having a soldering iron in one hand and keyboard in another. They program microprocessors in a style which may look old-fashion, but it is the only possible if you have devices with 8 MHz CPU and 4 kB RAM. Pentiums will never replace MPU's same as birds will never replace insects. My approach from theoretical point of view is bad programming practice (I agree) but from practical point of view it gives real profits. For example I developed program for PC-controller working under FreeDOS (which is still in use when you need real time operation) and I need to migrate it on CellPhone. Using my approach it will take an hour as source code will be practically the same, what you say will take a month.
Sorry, I think this is the worst kind of thing to do. Here's why:
1. Java isn't that much different from C, you could just go ahead and learn it instead of spending all the time to rewrite C functions in Java.
2. You can't really use C anyway, because you have to remember a bunch of caveats as outlined in your article (java types, subroutine differences, pointers, etc.)
3. The person who has to maintain this mess after you are gone will probably end up rewriting it anyway.
Some of your library seems to have good functionality; frankly though, I'm not sure I'd trust it since you seem so stuck in Borland C land that you can't move on to another language.
First of all thank you for detailed though negative responce. I am rather old programmer and I've started when programming started as such. I've pasted through Fortran from PDP to FPS4, C, C++, PHP, and my mind now is like writen completely CD-ROM. Now I am MPU-programmer (it's microprocessors) and the article is first of all for MPU-programmers. They program partly on assembler and partly on special classical C for MPU (not Borland C++). But like most MPU-programmers I have to deal with "large PC" for debugging my firmware and control MPU. I do service software for my firmware for Windows, Linux, PDA and Cell Phone platforms as my devices must work in different hands. I try to use the same source code for all these platforms (plus it is very close to MPU-program). Part of this work was done by Microsoft who made EVC++ very close to VC++, another important part was done by WINE developers, whose software I use successfully (I just use Win32 executables with Wine on Linux). But there was a gap in J2ME, and I decided to fill it. Some years of experience showed high efficiency of this approach.
It is nice that you've noticed functionality of my functions: it was tested on hundreds of practical tasks. I will say more: this set of functions is all-sufficient for real practical tasks. Of cause all programs can have bugs, and my software is not as good at Microsoft's but I am developer of on-board systems where reliability must be high.
Best regards Michael.
If you just need to send any file from computer to computer via BlueTooth using MS Windows standard means it is very easy: click with right mouse button the file you need to send, select in opened popup "Send" + "BlueTooth" and then just carefully answer some questions from Windows on both computers.
It is more difficult to do the same from your application on one computer to your application on another computer. My article can help you. Find my download sample files: bluetoth.java and file.java. In bluetooth.java it is shown how to communicate between 2 devices via BlueTooth using RFCOMM service or Virtual COM-port (VCP). Using it you can send any type of data including files. What you must do is: 1) Open communication channel based on VCP using "ComOpen"- commands with Server on one side and Client on the other. 2) On one side read your file to buffer using my "read"-command and then send it to COM-port using "ComWrite"-command. 3) On the other side do the same in back order: read data from COM-port to buffer using "ComRead"-command and then write it to file using "write" command.
Software in the article is devoted to CellPhone MIDP System only. If you visit my site quoted in the article you can find there information how to do it on PC's under Windows or Linux or PDA with Windows Mobile.