Yes, fpc3.04 breaks this component:
In unit pparser.pp (fpc/packages/fpc-passrc/src)
//fpc 3.04:
function TPasTreeContainer.CreateFunctionType(const AName, AResultName: String;
AParent: TPasElement; UseParentAsResultParent: Boolean;
const ASrcPos: TPasSourcePos): TPasFunctionType;
// fpc.3.02:
function TPasTreeContainer.CreateFunctionType(const AName, AResultName: String;
AParent: TPasElement; UseParentAsResultParent: Boolean;
const ASourceFilename: String; ASourceLinenumber: Integer): TPasFunctionType;
BTW, I see that this component requires packages wst_indy and wst_synapse. I did not test - but what happens if the "original" packages are already installed? Don't we have a lot of naming conflicts then?
@GetMem: Sorry to hijack this thread, but when trying to install wst with OnlinePackageManager I saw the attached painting glitch in a localized form (label "Geschwindigkeit" overlapping with value).