u

Author: thradams

manual.md

@@ -6,6 +6,8 @@ This approach makes Cake useful in real and existing programs.
 
 When applicable, Cake uses the same command line options of MSVC and GCC.
 
+For static analysis see: [ownership](ownership.html)
+
 ### Include directories
 
 Include directories are specified in `cakeconfig.h` file.
@@ -2306,9 +2308,6 @@ We have some compile time functions to infer properties of types.
 
 ```c
 
-_is_char()
-The three types char, signed char, and unsigned char are collectively called the character types.
-
 _is_pointer
 Pointer to object or function
 
@@ -2318,24 +2317,10 @@ Array type
 _is_function
 A function type describes a function with specified return type. 
 
-_is_floating_point
-float, double, and long double return true
-
-_is_integral
-The standard signed integer types and standard unsigned integer types are collectively called the
-standard integer types;
-
-_is_arithmetic
-Integer and floating types are collectively called arithmetic types. 
-
-_is_scalar
-Arithmetic types, pointer types, and the nullptr_t type are collectively called scalar types
-
 ```
 
-Note: Type traits that can be easily created with \_Generic will be removed.
 _
-### Extension - Object lifetime checks
+### Object lifetime checks
 
 See [ownership](ownership.html)
 

ownership.md

@@ -1,5 +1,5 @@
 
-Last Updated 3 March 2025
+Last Updated 5 December 2025
 
 This is a work in progress. Cake source is currently being used to validate the concepts. It's in the process of transitioning to include annotated nullable checks, which was the last feature added.  
 
@@ -159,42 +159,8 @@ If `is_empty` changes, it could potentially invalidate the assert on the caller'
 Although a runtime check is in place, it is not as safe as a compile-time check because it may occur 
 within a rarely used branch, allowing the bug to remain inactive.
 
-For this reason, a 'contract' approach is also being developed in Cake, *__although it 
-is still in the early stages of design__*.
-
-We can specify the post-conditions for the results of true and false branches using `true` and `false`
-at the function declaration, as well as for void functions using `post`
-
-```c
-#pragma safety enable
-
-struct X {
-    int * _Opt data;
-};
-
-bool is_empty(const struct X * p)
-  true(p->data == 0),
-  false(p->data != 0)
-{
-    return p->data == nullptr;
-}
-
-void clear(struct X * p)
-  post(p->data == 0)  
-{
-    p->data = nullptr;
-}
-
-void f(struct X * p) 
-{
-   if (!is_empty(p)) {      
-      /*assert not required anymore*/
-      *p->data = 1;
-   }
-}
-```  
-
-<button onclick="Try(this)">try</button>
+For this reason, a 'contract' approach is also being developed in Cake with the objective of moving
+the assert to function `is_empty` contract.
 
 The advantage of contracts, as mentioned earlier, is that the postconditions are 
 located in a single place. This is useful not only to avoid code repetition but 
@@ -203,9 +169,6 @@ which are assumed to be true and may be dangerous if they are out of sync
 with the implementation.
 On the other hand, placing the contracts alongside the function declaration 
 keeps the contract closer to its implementation. 
-Compilers (though Cake is not currently doing this yet) could create proxy 
-functions to check postconditions at runtime. (See C++ 26 contracts)
-
 
 
 #### Non nullable members initialization
@@ -309,17 +272,7 @@ void f() {
 
 <button onclick="Try(this)">try</button>
 
-We could remove this built-in some something like
-
-```c
-#pragma nullable enable  
-_Uninitialized void * _Opt malloc(unsigned int sz);
-```
-
-This is not implemented yet.
-
-
- `calloc` has a built in semantics indicating the object is zero-initialized. 
+`calloc` has a built in semantics indicating the object is zero-initialized. 
 
 ```c
 #pragma nullable enable  
@@ -454,7 +407,7 @@ struct X * _Opt makeX(const char* name)
 Since mutability may be useful for constructors and destructors, 
 the idea of mutable could imply that change may happen only once. 
 This naturally occurs when assigning a non-nullable pointer for the 
-first time—because afterward, it cannot become nullable again. 
+first time—because afterward, it cannot become nullable again. 
 Similarly, for const objects, it could mean that once initialized, 
 a const object cannot change anymore. In this context, 'constructor' 
 or 'destructor' might be a more suitable term.
@@ -1542,7 +1495,7 @@ int f(int c)
 ```
 
 In the following example, Cake recognizes that the pointed object is 'maybe deleted.' 
-However, if the object is deleted, it doesn’t matter because the pointer is null. 
+However, if the object is deleted, it doesn’t matter because the pointer is null. 
 These relationships between states are not tracked.
 
 ```c

src/cakeconfig.h

@@ -1,12 +1,11 @@
 //This was generated by running cake -autoconfig 
 //This file was generated reading the variable INCLUDE inside Visual Studio Command Prompt.
 //echo %INCLUDE% 
-#pragma dir "C:/Program Files/Microsoft Visual Studio/2022/Professional/VC/Tools/MSVC/14.44.35207/include/"
-#pragma dir "C:/Program Files/Microsoft Visual Studio/2022/Professional/VC/Tools/MSVC/14.44.35207/ATLMFC/include/"
-#pragma dir "C:/Program Files/Microsoft Visual Studio/2022/Professional/VC/Auxiliary/VS/include/"
+#pragma dir "C:/Program Files/Microsoft Visual Studio/2022/Community/VC/Tools/MSVC/14.44.35207/include/"
+#pragma dir "C:/Program Files/Microsoft Visual Studio/2022/Community/VC/Tools/MSVC/14.44.35207/ATLMFC/include/"
+#pragma dir "C:/Program Files/Microsoft Visual Studio/2022/Community/VC/Auxiliary/VS/include/"
 #pragma dir "C:/Program Files (x86)/Windows Kits/10/include/10.0.26100.0/ucrt/"
 #pragma dir "C:/Program Files (x86)/Windows Kits/10//include/10.0.26100.0//um/"
 #pragma dir "C:/Program Files (x86)/Windows Kits/10//include/10.0.26100.0//shared/"
 #pragma dir "C:/Program Files (x86)/Windows Kits/10//include/10.0.26100.0//winrt/"
 #pragma dir "C:/Program Files (x86)/Windows Kits/10//include/10.0.26100.0//cppwinrt/"
-#pragma dir "C:/Program Files (x86)/Windows Kits/NETFXSDK/4.8/include/um/"

src/file.c

@@ -1,6 +1,8 @@
-void f(int n)
+#pragma safety enable
+
+struct X { char* s; };
+struct X f()
 {
-    goto  target;
-    int a[n];    
-    target:
+    struct X x = {};
+    return x;
 }