英文字典中文字典


英文字典中文字典51ZiDian.com



中文字典辞典   英文字典 a   b   c   d   e   f   g   h   i   j   k   l   m   n   o   p   q   r   s   t   u   v   w   x   y   z       







请输入英文单字,中文词皆可:

vaxocentrism    
/vak"soh-sen"trizm/ [analogy with "ethnocentrism"] A notional
disease said to afflict C programmers who persist in coding
according to certain assumptions that are valid (especially
under Unix) on {VAXen} but false elsewhere. Among these are:

1. The assumption that dereferencing a null pointer is safe
because it is all bits 0, and location 0 is readable and 0.
Problem: this may instead cause an illegal-address trap on
non-VAXen, and even on VAXen under OSes other than BSD Unix.
Usually this is an implicit assumption of sloppy code
(forgetting to check the pointer before using it), rather than
deliberate exploitation of a misfeature.

2. The assumption that characters are signed.

3. The assumption that a pointer to any one type can freely be
cast into a pointer to any other type. A stronger form of
this is the assumption that all pointers are the same size and
format, which means you don't have to worry about getting the
casts or types correct in calls. Problem: this fails on
word-oriented machines or others with multiple pointer
formats.

4. The assumption that the parameters of a routine are stored
in memory, on a stack, contiguously, and in strictly ascending
or descending order. Problem: this fails on many RISC
architectures.

5. The assumption that pointer and integer types are the same
size, and that pointers can be stuffed into integer variables
(and vice-versa) and drawn back out without being truncated or
mangled. Problem: this fails on segmented architectures or
word-oriented machines with funny pointer formats.

6. The assumption that a data type of any size may begin at
any byte address in memory (for example, that you can freely
construct and dereference a pointer to a word- or
greater-sized object at an odd char address). Problem: this
fails on many (especially RISC) architectures better optimised
for {HLL} execution speed, and can cause an illegal address
fault or bus error.

7. The (related) assumption that there is no padding at the
end of types and that in an array you can thus step right from
the last byte of a previous component to the first byte of the
next one. This is not only machine- but compiler-dependent.

8. The assumption that memory address space is globally flat
and that the array reference "foo[-1]" is necessarily valid.
Problem: this fails at 0, or other places on segment-addressed
machines like Intel chips (yes, segmentation is universally
considered a {brain-damaged} way to design machines (see
{moby}), but that is a separate issue).

9. The assumption that objects can be arbitrarily large with
no special considerations. Problem: this fails on segmented
architectures and under non-virtual-addressing environments.

10. The assumption that the stack can be as large as memory.
Problem: this fails on segmented architectures or almost
anything else without virtual addressing and a paged stack.

11. The assumption that bits and addressable units within an
object are ordered in the same way and that this order is a
constant of nature. Problem: this fails on {big-endian}
machines.

12. The assumption that it is meaningful to compare pointers
to different objects not located within the same array, or to
objects of different types. Problem: the former fails on
segmented architectures, the latter on word-oriented machines
or others with multiple pointer formats.

13. The assumption that an "int" is 32 bits, or (nearly
equivalently) the assumption that "sizeof(int) ==
sizeof(long)". Problem: this fails on {PDP-11s}, {Intel
80286}-based systems and even on {Intel 80386} and {Motorola
68000} systems under some compilers.

14. The assumption that "argv[]" is writable. Problem: this
fails in many embedded-systems C environments and even under a
few flavours of Unix.

Note that a programmer can validly be accused of vaxocentrism
even if he or she has never seen a VAX. Some of these
assumptions (especially 2--5) were valid on the {PDP-11}, the
original {C} machine, and became endemic years before the VAX.
The terms "vaxocentricity" and "all-the-world"s-a-VAX
syndrome' have been used synonymously.

[{Jargon File}]

vaxocentrism: /vak`soh·sen´trizm/, n. [analogy withethnocentrism’] A notional disease said
to afflict C programmers who persist in coding according to certain
assumptions that are valid (esp. under Unix) on
VAXen but false elsewhere. Among these are:

  1. The assumption that dereferencing a null pointer is safe because it is all
    bits 0, and location 0 is readable and 0. Problem: this may instead cause an
    illegal-address trap on non-VAXen, and even on VAXen under OSes other than BSD
    Unix. Usually this is an implicit assumption of sloppy code (forgetting to
    check the pointer before using it), rather than deliberate exploitation of a
    misfeature.

  2. The assumption that characters are signed.

  3. The assumption that a pointer to any one type can freely be cast into a
    pointer to any other type. A stronger form of this is the assumption that all
    pointers are the same size and format, which means you don't have to worry
    about getting the casts or types correct in calls. Problem: this fails on
    word-oriented machines or others with multiple pointer formats.

  4. The assumption that the parameters of a routine are stored in memory, on a
    stack, contiguously, and in strictly ascending or descending order. Problem:
    this fails on many RISC architectures.

  5. The assumption that pointer and integer types are the same size, and that
    pointers can be stuffed into integer variables (and vice-versa) and drawn back
    out without being truncated or mangled. Problem: this fails on segmented
    architectures or word-oriented machines with funny pointer formats.

  6. The assumption that a data type of any size may begin at any byte address in
    memory (for example, that you can freely construct and dereference a pointer
    to a word- or greater-sized object at an odd char address). Problem: this
    fails on many (esp. RISC) architectures better optimized for
    HLL execution speed, and can cause an illegal address
    fault or bus error.

  7. The (related) assumption that there is no padding at the end of types and that
    in an array you can thus step right from the last byte of a previous component
    to the first byte of the next one. This is not only machine- but
    compiler-dependent.

  8. The assumption that memory address space is globally flat and that the array
    reference foo[-1] is necessarily valid.
    Problem: this fails at 0, or other places on segment-addressed machines like
    Intel chips (yes, segmentation is universally considered a
    brain-damaged way to design machines (see
    moby), but that is a separate issue).

  9. The assumption that objects can be arbitrarily large with no special
    considerations. Problem: this fails on segmented architectures and under
    non-virtual-addressing environments.

  10. The assumption that the stack can be as large as memory. Problem: this fails
    on segmented architectures or almost anything else without virtual addressing
    and a paged stack.

  11. The assumption that bits and addressable units within an object are ordered in
    the same way and that this order is a constant of nature. Problem: this fails
    on big-endian machines.

  12. The assumption that it is meaningful to compare pointers to different objects
    not located within the same array, or to objects of different types. Problem:
    the former fails on segmented architectures, the latter on word-oriented
    machines or others with multiple pointer formats.

  13. The assumption that an int is 32 bits, or (nearly equivalently)
    the assumption that sizeof(int) ==
    sizeof(long)
    . Problem: this fails on PDP-11s, 286-based systems and
    even on 386 and 68000 systems under some compilers (and on 64-bit systems like
    the Alpha, of course).

  14. The assumption that argv[] is
    writable. Problem: this fails in many embedded-systems C environments and even
    under a few flavors of Unix.
Note that a programmer can validly be accused of vaxocentrism even if
he or she has never seen a VAX. Some of these
assumptions (esp. 2--5) were valid on the PDP-11,
the original C machine, and became endemic years before the VAX. The terms
vaxocentricity and all-the-world's-a-VAX syndrome have been used
synonymously.


请选择你想看的字典辞典:
单词字典翻译
vaxocentrism查看 vaxocentrism 在百度字典中的解释百度英翻中〔查看〕
vaxocentrism查看 vaxocentrism 在Google字典中的解释Google英翻中〔查看〕
vaxocentrism查看 vaxocentrism 在Yahoo字典中的解释Yahoo英翻中〔查看〕





安装中文字典英文字典查询工具!


中文字典英文字典工具:
选择颜色:
输入中英文单字

































































英文字典中文字典相关资料:


  • Recherche – Microsoft Bing
    Effectuez des recherches avec Microsoft Bing et utilisez la puissance de l’IA pour rechercher des informations, explorer des pages web, des images, des vidéos, des cartes, etc Un moteur de recherche intelligent pour les éternels curieux
  • Microsoft Bing | Get to know Bing
    Copilot Search in Bing gives you quick, summarized answers with cited sources and suggestions for further exploration, making it easier than ever to discover more
  • How To See All Bing Related Searches - TechYorker
    The most common place related searches appear is at the bottom of the Bing search results page This section is typically labeled with language like “Related searches” or “People also search for,” depending on the query type and layout Each suggestion is clickable and instantly runs a new search
  • How To See All Bing Related Searches - Position Is Everything
    You cannot see every Bing related search in one complete official list, but you can uncover many of them by checking the results page, autocomplete, search tabs, settings, and Microsoft’s research tools
  • How to See All Bing Related Searches - MacMyths
    Bing Related Searches appear after a search has already been performed, typically at the bottom of the SERP or embedded mid-page on some layouts These suggestions are reactive rather than predictive
  • bing related search version Crossword Clue | Wordplays. com
    Enter the crossword clue and click "Find" to search for answers to crossword puzzle clues Crossword answers are sorted by relevance and can be sorted by length as well
  • Bing : tout savoir sur le moteur de recherche de Microsoft
    Bing IA, aussi connu sous le nom Copilot Search, est l’évolution du moteur Bing lancée en avril 2025 Il combine recherche traditionnelle et IA générative (modèles GPT‑5 Prometheus) pour fournir des réponses enrichies, résumées avec sources et suggestions interactives
  • Microsoft Bing - Wikipedia
    Bing offers a broad spectrum of search services, encompassing web, video, image, and map search products, all developed using ASP NET The transition from Live Search to Bing was announced by Microsoft CEO Steve Ballmer on May 28, 2009, at the All Things Digital conference in San Diego, California The official release followed on June 3, 2009
  • Bing Testing Related Searches That Expand To More
    Microsoft is testing expandable related searches in the Bing Search results When you hover your mouse cursor over the related searches, Bing will load more below them
  • Télécharger Microsoft Bing (gratuit) Web, iOS, Android - Clubic
    Microsoft Bing est un moteur de recherche sur le Web développé et détenu par Microsoft Il a été lancé en 2009 pour remplacer le moteur de recherche précédent de la société, Live Search





中文字典-英文字典  2005-2009