英文字典中文字典


英文字典中文字典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英翻中〔查看〕





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


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

































































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


  • Yahoo Mail | Email with smart features and top-notch security
    Yahoo Mail: Your smarter, faster, free email solution Organize your inbox, protect your privacy, and tackle tasks efficiently with AI-powered features and robust security tools
  • Yahoo Mail
    It's time to get stuff done with Yahoo Mail Just add your Gmail, Outlook, AOL or Yahoo Mail to get going We automatically organise all the things life throws at you, such as receipts and attachments, so you can find what you need fast Plus, we've got your back with other convenient features such as one-tap unsubscribe, free trial expiry alerts and package tracking
  • Iniciar sesión - Iniciar sesión en Yahoo
    Es hora de ponerte en marcha con Yahoo Mail Solo tienes que añadir tu Gmail, Outlook, AOL o Yahoo Mail para empezar Organizamos automáticamente todo el contenido de tu correo, como recibos y archivos adjuntos, para que puedas encontrar lo que necesitas rápidamente Además, te lo ponemos aún más fácil con prácticas funciones como la cancelación de suscripciones con un solo toque, las
  • Yahoo Mail
    It's time to get stuff done with Yahoo Mail Just add your Gmail, Outlook, AOL or Yahoo Mail to get going We automatically organize all the things life throws at you, like receipts and attachments, so you can find what you need fast Plus, we've got your back with other convenient features like one-tap unsubscribe, free trial expiration alerts and package tracking
  • Log in - Sign in to Yahoo
    Sign in to access the best in class Yahoo Mail, breaking local, national and global news, finance, sports, music, movies You get more out of the web, you get more out of life
  • Yahoo Mail
    Es ist an der Zeit, Dinge mit Yahoo Mail zu erledigen Fügen Sie einfach Ihren Gmail-, Outlook-, AOL- oder Yahoo Mail-Account hinzu, um loszulegen Wir organisieren automatisch alle Dinge des Alltags, wie Quittungen und Anhänge, damit Sie schnell finden, was Sie brauchen Darüber hinaus unterstützen wir Sie mit weiteren praktischen Funktionen wie dem Abmelden durch einfaches Tippen
  • Iniciar sesión - Ingresar en Yahoo
    Accede a Yahoo Mail para disfrutar del mejor correo electrónico y estar al día con noticias, finanzas, deportes, música y más
  • Yahoo Mail
    È ora di aumentare la tua efficienza con Yahoo Mail Basta aggiungere Gmail, Outlook, AOL o Yahoo Mail per iniziare Organizziamo automaticamente tutti i documenti che ricevi, come ricevute e allegati, in modo che tu possa trovare rapidamente ciò di cui hai bisogno Inoltre, ti offriamo altre funzioni utili come l'annullamento delle iscrizioni con un tocco solo, gli avvisi di scadenza delle
  • Yahoo Mail
    Ήρθε η ώρα να οργανωθείτε με το Yahoo Mail Απλώς προσθέστε το Gmail, το Outlook, το AOL ή το Yahoo Mail για να ξεκινήσετε Οργανώνουμε αυτόματα όλα όσα μπορούν να βρεθούν στα εισερχόμενά σας, όπως αποδείξεις και συνημμένα, ώστε να
  • Yahoo Mail
    Aumento a sua produtividade com a ajuda do Yahoo Mail Basta adicionar seu Gmail, Outlook, AOL ou Yahoo Mail para começar Organizamos recibos e anexos automaticamente, para que você encontre rapidamente o que precisa Além disso, oferecemos outros recursos convenientes, como cancelamento de inscrição em listas de envio com apeans um toque, alertas de expiração de avaliações gratuitas





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