I need them one day to better understand xsd:choice mapping to C# for both XSD and WSDL usage.
I have the feeling that the WSDL and XSD importer are trying to be smart, so for instance when you have multiple choices that come down to a common basic type like a derivation from xsd:string, it makes to two properties: a C# enumeration to select the type and a C# string value for the content referencing the enumeration through a XmlChoiceIdentifierAttribute.
Recently I had to play some notification sounds in a Windows Delphi application where the application deployment should be as easy as possible: preferable copying the EXE around.
The thing that more recent Delphi versions made a lot easier is embedding WAV files as WAVE resources, more on that further on. Read the rest of this entry »
Two very interesting videos showing some background information as it is extremely hard to anonymise data. Not just for now, but especially against future de-anonymisation efforts.
You always have to be careful with Delphi finalization sections cleaning up things that might have not created inside the corresponding initialization section. This is especially true for the System unit.
That one actually contains this little piece of code that is being called after FinalizeUnits is called which also fianalises external memory managers like FastMM:
{$IFDEF MSWINDOWS}
FinalizeLocaleDate;
if PreferredLanguagesOverride <> nil then
FreeMem(PreferredLanguagesOverride);
...
Which means that you will have to enable the NeverUninstall conditional define as soon as the InstHashMap has been used.
Most often that’s the case with FMX applications that heavily relies on weak references.
The same holds for PreferredLanguagesOverride which is used by SetLocaleOverride and can be worked around by performing this right at the end of the .dpr:
I think that for cross platform and especially mobile development means you need to use tools from vendors that live and breathe that, by constantly showing they master these subjects for instance having good apps in the app stores and examples that are regularly updated to the ever changing field.
I really wonder what the rest of the Delphi community thinks about that.
The big problem in both cases is a formal language specification. The lack of a formal language specification makes it very hard to predict the effect of use cases or generate them for testing.
So this post is yet another request: Please Embarcadero/Idera, come up with a formal language definition for Delphi.
The Wiert Corner - irregular stream of stuff 