On Wed, 22 Aug 2007 11:16:12 +0200 Ron Blaschke <[EMAIL PROTECTED]> wrote: > >> Don't know if its a problem if they fail. I don't have a problem > >> with failures as they tell me there's something that needs > >> attention. > > > True. Well, these issues do need attention, so maybe they *should* > > fail. :) > > Jerry mentioned yesterday that there shouldn't be any failures for a > release, which makes sense as it would only upset users. Maybe there > should be a ticket for the failures then? Or an environment variable > like PARROT_PORTER which makes all tests fail that are skipped because > they are broken, not because the feature is not supported on the > platform?
Or maybe we should wait until the release, then stop skipping the error, which should help ensure it gets fixed before the next release. (It is a pretty important issue, I think, so I don't want to mask it any longer than absolutely necessary. Embeddability is important to me.) > Many thanks for helping with the t/src issues, I'm glad you jumped on > the Windows train. Some things work differently on Windows and Visual > C++, especially the linking and loading part, with symbol > exports/imports on the very top. > > One great way to find out about compiled objects, libraries and > executables is the COFF/PE Dumper (dumpbin), which shows details about > the binary image. Another fine tool is the Dependency Walker > (depends), which exactly shows you which libraries would be loaded, > including their full path, what symbols they export and which they > import. Great, good tips. I don't know if I'm really on the "windows train", though. I'm still primarily linux with a bit of freebsd on the side; for me, win32 is mostly in the category of "bizarre platform to make portability testing more interesting". But it will be good to know my way around a little bit better, so I can solve things more quickly next time. :) > Please don't hesitate to ask if you have any questions. Depending on > $job workload it might take some time before I can get back to you, > though. I know the feeling. Thanks! Mark
