انجمن‌های فارسی اوبونتو

کمک و پشتیبانی => برنامه‌سازی => نویسنده: Mmjafari در 18 امرداد 1396، 05:55 ب‌ظ

عنوان: وظایف شل
ارسال شده توسط: Mmjafari در 18 امرداد 1396، 05:55 ب‌ظ
سلام
یک شل به دقیقا چه کاری باید انجام بده؟
عنوان: پاسخ : وظایف شل
ارسال شده توسط: سلمان م. در 18 امرداد 1396، 06:49 ب‌ظ
پوسته (https://fa.wikipedia.org/wiki/%D9%BE%D9%88%D8%B3%D8%AA%D9%87_(%D8%B1%D8%A7%DB%8C%D8%A7%D9%86%D9%87)) (در ویکی‌پدیا)
عنوان: پاسخ : وظایف شل
ارسال شده توسط: فاروق در 18 امرداد 1396، 08:57 ب‌ظ
From The Jargon File (version 4.4.7, 29 Dec 2003) [jargon]:

  shell
   n.
 
      [orig. {Multics} techspeak, widely propagated via Unix]
 
      1. [techspeak] The command interpreter used to pass commands to an
      operating system; so called because it is the part of the operating system
      that interfaces with the outside world.
 
      2. More generally, any interface program that mediates access to a special
      resource or {server} for convenience, efficiency, or security reasons; for
      this meaning, the usage is usually a shell around whatever. This sort of
      program is also called a wrapper.
 
      3. A skeleton program, created by hand or by another program (like, say, a
      parser generator), which provides the necessary {incantation}s to set up
      some task and the control flow to drive it (the term {driver} is sometimes
      used synonymously). The user is meant to fill in whatever code is needed to
      get real work done. This usage is common in the AI and Microsoft Windows
      worlds, and confuses Unix hackers.
 
      Historical note: Apparently, the original Multics shell (sense 1) was so
      called because it was a shell (sense 3); it ran user programs not by
      starting up separate processes, but by dynamically linking the programs
      into its own code, calling them as subroutines, and then dynamically
      de-linking them on return. The VMS command interpreter still does something
      very like this.