Hi Rob, > issue a warning with a mismatch. But only in case the compiler is older > than the version mentioned in the included file (we would have to update > all files with every new compiler release otherwise).
Or... we could create a generic jallib include that is included by every other lib and handle supported compiler versions: - older versions that are known not to work with one or more libs throw an error like "jallib does not work properly with your compiler version. Please use compiler version x.y, that comes with this version of jallib' - older (but probably functional) versions like 'your compiler is old, please concider to update' - newer versions give a warning "jallib is tested on an older compiler version. Please report any issues to..." - the version we used for testing does not generate a message. Joep --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "jallib" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/jallib?hl=en -~----------~----~----~----~------~----~------~--~---
