I think it will be relative easy to deal with different compiler and different operating system. However, ICU does contain some C++ code. It will make life much harder, since current Parrot only assume ANSI C (even a subset of it).
Hong > This is rather concerning to me. As I understand it, one of > the goals for > parrot was to be able to have a usable subset of it which is totally > platform-neutral (pure ANSI C). If we start to depend too much on > another library which may not share that goal, we could have trouble > with the parrot build process (which was supposed to be > shipped as parrot bytecode)
