Path: ...!weretis.net!feeder9.news.weretis.net!news.nk.ca!rocksolid2!i2pn2.org!.POSTED!not-for-mail
From: fir <fir@grunge.pl>
Newsgroups: comp.lang.c
Subject: theorethical thought on tree structure, fields, tags and so called
 tag system (oryginal)
Date: Sun, 25 Aug 2024 16:17:22 +0200
Organization: i2pn2 (i2pn.org)
Message-ID: <117bbbb6a2baef294a5f8f489eddb9e5bf1f06fe@i2pn2.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Injection-Date: Sun, 25 Aug 2024 14:17:34 -0000 (UTC)
Injection-Info: i2pn2.org;
	logging-data="3850439"; mail-complaints-to="usenet@i2pn2.org";
	posting-account="+ydHcGjgSeBt3Wz3WTfKefUptpAWaXduqfw5xdfsuS0";
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:27.0) Gecko/20100101 Firefox/27.0 SeaMonkey/2.24
X-Spam-Checker-Version: SpamAssassin 4.0.0
Bytes: 2628
Lines: 64

[i added teh tag oryginal - as in fact most of what i write aroound c
language theory are oryginal thoughts, not something that i just read or 
seen somewhere - to be clear)

i thought a bot on things like that

some {

   void a() {}
   void b() {}
}

some2 {

   void a() {}
   void b() {}
}

and soem obserwation is its probably more convenient to
write

   void some.a() {}
   void some.b() {}
   void some2.a() {}
   void some2.b() {}

wchich my be seen as critique of this module {} convention
(where opening s far to closing

then you can call foo(some) or foo(some2) for some advantage

but if so this convention will probably build a tree
structure over the fields and i once noticed tree
structure is not best for some things (liek in need
for soem things people calls polymorphism)

it seems something i call 'tags' is better - it is
situation ehen given thing has more than one parent
but im not sure how to 'bite' this

say soem example

     car.wheels
     car.doors
     car.engine
     car.move()

     boat.engine
     boat.turbine
     boat.move()

car is vehicle, and say when car in programming
world is full structure the vehicle is probably more
the interface that car should give as its vehicle

so "vehicle" is something other than auperfield
(or how to call it) it must be something other,
maybe i should call it tags

im not in mood to write on it more today (not much good
form and focus) but from this whai i write imo
teh conclusion is probably - treelike structures and fields
are not enough to do what is called polymorphism
(and soem interface related things) so there is a need
of define soem "tag system" probably aside of that