WelcomeWelcome | FAQFAQ | DownloadsDownloads | WikiWiki

Author Topic: Why using different commands for extensions ?  (Read 3201 times)

Offline Pats

  • Sr. Member
  • ****
  • Posts: 322
Why using different commands for extensions ?
« on: January 29, 2010, 02:55:42 AM »
There are diff commands ( TCL2.8rc4 ) like tce-load, tce-update, etc for diff operations but related to extensions only. Why these related commands were not combined in tce-load like -i options ( for eq: tce-load -u for update ) and so on... any special reason from the users and developers poview ?
Just curious !
~ Pats

Offline gerald_clark

  • TinyCore Moderator
  • Hero Member
  • *****
  • Posts: 4254
Re: Why using different commands for extensions ?
« Reply #1 on: January 29, 2010, 05:46:32 PM »
Maybe you would also rather do
busybox ls
busybox rm
busybox cat

Offline mikshaw

  • Sr. Member
  • ****
  • Posts: 368
Re: Why using different commands for extensions ?
« Reply #2 on: January 30, 2010, 11:54:11 AM »
I'd say it's mainly to keep it simple.  Combining several commands into a single script adds an extra layer of complexity, in that the script has to parse arguments to determine which task is to be done.  Keeping them in separate scripts allows the script to do one task, without the need to be told which task.  Either way works, but this method goes along with the traditional *nix practice of having a collection of small tools that each do one job as well as it can.

Offline curaga

  • Administrator
  • Hero Member
  • *****
  • Posts: 11049
Re: Why using different commands for extensions ?
« Reply #3 on: January 30, 2010, 04:33:08 PM »
They wouldn't really share code, so combining them would have little benefit.
The only barriers that can stop you are the ones you create yourself.

Offline Pats

  • Sr. Member
  • ****
  • Posts: 322
Re: Why using different commands for extensions ?
« Reply #4 on: January 31, 2010, 05:22:06 AM »
- I'd say it's mainly to keep it simple -
No offence intended towards a senior like you, but if-then-fi or case-esae is also not that complicated. And I think these small utils are not that complicated to code.
- ... goes along with the traditional unix practice... -
What abt emacs ? It does lots of diff things in one app. :)

- They wo'nt really share code... -
Yah, more logical but is it other way round ? Just - dpkg - ligacy - continued ?
Or may be lack of time to code ( or re-invent  ) again ? I know there are other imp utils/apps to be tcz-ed for the repo. :)
Pl take it lightly - I was just figuring out how senior devlopers work and think ! :)

~ Pats

Offline MakodFilu

  • Newbie
  • *
  • Posts: 46
Re: Why using different commands for extensions ?
« Reply #5 on: February 02, 2010, 10:36:35 PM »
if-then-fi or case-esae is also not that complicated
True.

Quote
And I think these small utils are not that complicated to code.
Possibly not.

Just please, post the resulting .tcz when you'll have figured out already the best way to integrate all.

P.S.: OTOH I think the remark made by gerald_clark is insightful and deserves some consideration.
« Last Edit: February 03, 2010, 12:58:10 AM by MakodFilu »