portability

I'm trying to code an application which runs un different java platforms like J2SE, J2ME, Android, etc. I already know that I'll have to rewrite most of the UI for each platform, but want to reuse the core logic. Keeping this core portable involves three drawbacks that I know of: Keeping to the old Java 1.4 syntax , not using any of the nice language features of Java 5.0 only using external libraries that are known to work on those platforms (that is: don't use JNI and don't have dependencies to other libs which violate this rules) only using the classes which are present on all those

If there is for example a class that requires a pointer and a bool . For simplicity an int pointer will be used in examples, but the pointer type is irrelevant as long as it points to something whose size() is more than 1 . Defining the class with { bool , int *} data members will result in the class having a size that is double the size of the pointer and a lot of wasted space If the pointer does not point to a char (or other data of size(1) ), then presumably the low bit will always be zero. The class could defined with {int *} or for convenience: union { int *, uintptr_t } The bool is

For a project at university I need to extend an existing C application, which shall in the end run on a wide variety of commercial and non-commercial unix systems (FreeBSD, Solaris, AIX, etc.). Which things do I have to consider when I want to write a C program which is most portable? The best advice I can give, is to move to a different platform every day, testing as you go. This will make the platform differences stick out like a sore thumb, and teach you the portability issues at the same time. Saving the cross platform testing for the end, will lead to failure. That aside Integer sizes can

I have been trying to find a good solution to this for a long time: Is there a sure-fire way to install ruby to a folder which is portable on that platform? I want to have a folder which I can easily copy into a distribution I am making so I can have a ruby environment "on the go". It is fine if I need to compile the source and stuff, as long as I end up with a portable ruby install. I have found a few resources which tries to solve this, but none are satisfactory for me. Portable Ruby on Rails environment http://hcettech.blogspot.pt/2012/05/windows-portable-rails-development.html For me this

I'm looking for a good and easy in maintenance portable build system for C++ projects. Main platforms should include Windows (Visual Studio 8+) and Linux (gcc); Cygwin may be an advantage. We're considering two main possibilities: CMake and Boost.Jam . SCons can be also an option, but I haven't investigated it yet. CMake and Boost.Jam seem to have the following traits: CMake: (+) generates native "makefile" (solution for Windows, project for Eclipse) (+) extensions for testing and packaging (-) demands a configuration file in every project folder (-) based on a little too verbose peculiar

I have a small Django project I received from a friend. The code works perfectly on his system. However, on my system I get the following error message when running the server: TemplateSyntaxError at / 'current_tags' is not a valid tag library: Template library current_tags not found, tried django.templatetags.current_tags The problem is with a line in an html file: {% load current_tags %} This exact same code works on his system with no errors. What could that be? mif I would suggest the following: (Most likely) You haven't installed one of the dependencies of your tag library. Check the