Dimensional Data

rocedure TForm1.Button1Click(Sender: TObject); var   P : Variant; begin   PythonEngine1.ExecStrings( Memo1.Lines );   P := MainModule.Person(‘John’, ‘Doe’);   Assert(P.first_name = ‘John’);   Assert(P.last_name = ‘Doe’);   Assert(VarIsNone(P.weight));   Assert(VarIsNone(P.height));   Assert(VarIsNone(P.age));   P := MainModule.Person(‘John’, ‘Doe’, weight := 70);   Assert(P.first_name = ‘John’);   Assert(P.last_name = ‘Doe’);   Assert(P.weight = 70);   Assert(VarIsNone(P.height));   Assert(VarIsNone(P.age));   P := MainModule.Person(‘John’, ‘Doe’, weight := 70, height := 172);   Assert(P.first_name = ‘John’);   Assert(P.last_name = ‘Doe’);   Assert(P.weight = 70);   Assert(P.height = 172);   Assert(VarIsNone(P.age));   P := MainModule.Person(‘John’, ‘Doe’, weight := 70, height := 172, age := 35);   Assert(P.first_name = ‘John’);   Assert(P.last_name = ‘Doe’);   Assert(P.weight = 70);   Assert(P.height = 172);   Assert(P.age = 35);   P := MainModule.Person(last_name := ‘Doe’, first_name := ‘John’, weight := 70, height := 172, age := 35);   Assert(P.first_name = ‘John’);   Assert(P.last_name = ‘Doe’);   Assert(P.weight = 70);   Assert(P.height = 172);   Assert(P.age = 35);   P := MainModule.Person(‘John’, ‘Doe’, 35, 172, 70);   Assert(P.first_name = ‘John’);   Assert(P.last_name = ‘Doe’);   Assert(P.weight = 70);   Assert(P.height = 172);   Assert(P.age = 35);   Memo2.Lines.Add(‘Success’) end;

Substitution failure is not an error (SFINAE) refers to a situation in C++ where an invalid substitution of template parameters is not in itself an error. We’re talking here about something related to templates, template substitution rules and metaprogramming… A quick example: template struct A {}; char xxx(int); char xxx(float); template A f(T){} int main() { f(1); }   template <int I> struct A {};     char xxx(int);   char xxx(float);     template <class T> A<sizeof(xxx((T)0))> f(T){}     int main()   {     f(1);   } This example is rejected by all major compilers because template deduction/substitution has historically used a simplified model of semantic checking, i.e., the SFINAE rules (which are mostly about types), instead of full semantic checking. But in C++ 11, fully general expressions allowed, and that most errors in such expressions be treated as SFINAE failures rather than errors. There’s a continuum of errors, some errors being clearly SFINAE failures, and some clearly “real” errors, with lots of unclear cases in between. We decided it’s easier to write the definition by listing the errors that are not treated as SFINAE failures, and the list we came up with is as follows: errors that occur while processing some entity external to the expression, e.g., an instantiation of a template or the generation of the definition of an implicitly-declared copy constructor. errors due to implementation limits (it’s probably a category error to list these here, since they’re not errors in the normal sense, but we wanted to make it very clear that compilers don’t have to take steps to capture and recover from violations of implementation limits; such violations cause hard errors, compiler crashes, etc., the same as anywhere else in a program). errors due to access violations (this is a judgment call, but the philosophy of access has always been that it doesn’t affect visibility)Everything else produces a SFINAE failure rather than a hard error. At certain points in the template argument deduction process it is is necessary to take a function type that makes use of template parameters and replace those template parameters with the corresponding template arguments. This is done at the beginning of template argument deduction when any explicitly specified template arguments are substituted into the function type, and again at the end of template argument deduction when any template arguments that were deduced or obtained from default arguments are substituted. The substitution occurs in all types and expressions that are used in the function type and in template parameter declarations. The expressions include not only constant expressions such as those that appear in array bounds or as nontype template arguments but also general expressions (i.e., non-constant expressions) inside sizeof, decltype, and other contexts that allow non-constant expressions. [Note: The equivalent substitution in exception specifications is done only when the function is instantiated, at which point a program is ill-formed if the substitution results in an invalid type or expression.] For example, template auto f(T t1, T t2) -> decltype(t1 + t2); template <class T> auto f(T t1, T t2) -> decltype(t1 + t2); Head over and check out more information about SFINAE problems for expressions in Windows Development.

procedure TForm1.Button2Click(Sender: TObject); var   _im : Variant;   _stream : TMemoryStream;   _dib : Variant;   pargs: PPyObject;   presult :PPyObject;   P : PAnsiChar;   Len : NativeInt; begin   if (Image1.Picture.Graphic = nil) or Image1.Picture.Graphic.Empty then     raise Exception.Create(‘You must first select an image’);   PythonEngine1.ExecStrings(Memo1.Lines);   _im := MainModule.ProcessImage(ImageToPyBytes(Image1.Picture.Graphic));   if not chkUseDC.Checked then   begin     // We have to call PyString_AsStringAndSize because the image may contain zeros     with GetPythonEngine do begin       pargs := MakePyTuple([ExtractPythonObjectFrom(_im)]);       try         presult := PyEval_CallObjectWithKeywords(             ExtractPythonObjectFrom(MainModule.ImageToBytes), pargs, nil);         try           if (P = nil) or (PyBytes_AsStringAndSize(presult, P, Len) 0) then begin             ShowMessage(‘This does not work and needs fixing’);             Abort;           end;         finally           Py_XDECREF(pResult);         end;       finally         Py_DECREF(pargs);       end;     end;       _stream := TMemoryStream.Create();     try       _stream.Write(P^, Len);       _stream.Position := 0;       Image1.Picture.Graphic.LoadFromStream(_stream);     finally       _stream.Free;     end;   end   else   begin     Image1.Picture.Bitmap.SetSize(Image1.Width, Image1.Height);     _dib := Import(‘PIL.ImageWin’).Dib(_im);     Image1.Picture.Bitmap.SetSize(Image1.Height, Image1.Width);     _dib.expose(NativeInt(Image1.Picture.Bitmap.Canvas.Handle));   end; end;

This FireMonkey UI template includes three different designs for implementing an app profile screen in a multi-device application. As you can see, these are the app profile Delphi/C++ Builder FireMonkey samples. From these sample app profile demos, you can learn how to design and build beautiful responsive FireMonkey applications by just dragging and dropping the components. Sample features Available on Delphi and C++ Builder TFrame TLayout TRectangle  and other components You can download these samples from GetIt Package Manager Also, be sure to check out other FireMonkey and VCL sample applications on GetIt

We are pleased to invite all of our RAD Studio customers with an active subscription to the NDA beta program for Embarcadero’s 10.4.2 release of Delphi, C++Builder, and RAD Studio, codenamed “Hunter”. RAD Studio 10.4.2 builds on the great features introduced in RAD Studio 10.4 and 10.4.1, and adds new features and enhancements throughout the product.  To learn more about the capabilities we have planned for the 10.4.2 release, please refer to the RAD Studio November 2020 Roadmap PM Commentary blog post (please note that features mentioned in the blog post are not committed until completed and GA released). After you have joined the beta, you will receive additional documentation detailing the features of each beta build. How to join:  To participate in the beta, please provide your name and the email address associated with your Update Subscription (the email you used to register the product) using this form by Tuesday, December 15, 2020. Once you’ve provided your email address, you will receive a follow-up email in the second half of December with a link to electronically sign the Hunter Beta NDA. After signing the NDA, you will be provided with the information needed to participate in the 10.4.2 beta. Please note that 10.4.2 beta builds cannot be installed on the same machine as your current 10.4 or 10.4.1 Sydney installation (also, we generally recommend against installing beta versions on a production machine).   Not current on subscription but interested in joining the 10.4.2 beta? Contact your Embarcadero sales representative or reseller partner to renew your subscription and be invited to join the beta program.