Conversation

Notices

1. Embed this notice
   Nroot (nroot@clubcyberia.co)'s status on Thursday, 25-Dec-2025 02:06:30 JST Nroot

   • :ihavenomouth:
   @Inginsub I am working on a simple OOP for TOSVER. TOSVER has to be good software because I dont want to maintain it.
   
   The OOP is designed to "removable" and will do nothing more than check class's validity,and garbage collect(when called,also will do leak-checking),there and CAlloc's will not be needed as there will be "pools" with strings to avoid StrNew/Free everytime.
   
   Once im done,the OOP functions will basically be removed as OOP here is just Assert-ing the correct type during devopement
   • Forest of Enchantment likes this.
   • Embed this notice
     :ihavenomouth: (inginsub@clubcyberia.co)'s status on Thursday, 25-Dec-2025 21:08:49 JST :ihavenomouth:

     in reply to

     @nroot I was thinking about adding class methods to HolyC, as syntactic sugar for stuff like array_insert(arr, idx, element) => arr->insert(idx, element), without overriding for descendants, and use those instead of macro expansions like this. It should be simple enough, since I reworked CHashClass and made it slightly more sane

   • Embed this notice
     :ihavenomouth: (inginsub@clubcyberia.co)'s status on Thursday, 25-Dec-2025 21:15:23 JST :ihavenomouth:

     in reply to

     • :ihavenomouth:
     @nroot I mean that arr->insert() will expand to e.g. __U64_p_dynamic_array__insert_ directly instead of going through several layers of macro injection
   • Embed this notice
     FrailLeaf (frailleaf@ryona.agency)'s status on Thursday, 25-Dec-2025 21:42:47 JST FrailLeaf

     in reply to

     • :ihavenomouth:
     @Inginsub @nroot >uti
     pal why you writing about uti in your software
     :ihavenomouth: likes this.