Welcome, Guest. Please login or register.

Author Topic: CreateNewProc bug in SASC ?  (Read 5595 times)

Description:

0 Members and 1 Guest are viewing this topic.

Offline Einstein

  • Sr. Member
  • ****
  • Join Date: Dec 2004
  • Posts: 402
    • Show all replies
Re: CreateNewProc bug in SASC ?
« on: September 19, 2007, 02:03:42 PM »
Quote
void CllFnc(void);


Quote
PrcTgs[0].ti_Tag = NP_Entry;


My Opinion:

Are we influenced by awkward Unix naming convention perhaps ?  :roll:
Nowadays I see other operating systems with clear, fully descriptive, and rationally named APIs, something Amiga should've done long ago, why do certain amiga programmers insist on going the unix convetion way ?

Why not just..

void CallFunction( void );
..
newProcessTags[ 0 ].ti_Tag = NP_Entry;

..?


Just to expand, things like:

window->RPort vs screen->RastPort
struct RastPort vs struct RasInfo (without a "t")
struct RasInfo vs struct Layer_Info (with an underscore)

 :-?

And these are just a few of the annoyances.

Just my opinion, no more rants lol.
I have spoken !
 

Offline Einstein

  • Sr. Member
  • ****
  • Join Date: Dec 2004
  • Posts: 402
    • Show all replies
Re: CreateNewProc bug in SASC ?
« Reply #1 on: September 27, 2007, 08:34:08 PM »
I agree, they are irrelevant when used privately, but in case of Open Source, or as formal APIs, unix like naming can be a real pain in the ass, float myCents = 0.000001;.
I have spoken !