I wasn't saying that there is no such thing as a $2 bill, that is what the joke is called since the clerks and manger didn't know about them and only when security was called, did they realize there is one and it still is used.
>________________________________ > From: Ron Pickard RPQ <[email protected]> >To: 'EMC-PSTC' <[email protected]> >Sent: Friday, March 1, 2013 8:53 AM >Subject: RE: a CAB person and my Python > > >Hi Bill, >The $2 bill is, in fact, still a current denomination of US currency, albeit >rarely used. It’s introduction was back in the mid-1800s, I believe. I still >have a few of them from many years ago. > >But, there was the $3 bill, but that only made it to be funny money. > >Best regards, > >Ron Pickard > >From:[email protected] [mailto:[email protected]] On Behalf Of Bill Owsley >Sent: Thursday, February 28, 2013 11:02 PM >To: [email protected]; 'EMC-PSTC' >Subject: Re: a CAB person and my Python > >And some of them are voters too!!! >Tonight at the grocery store, $50 back from the POS, and could you please >change this $20 for 2 tens? >I needed $60 and only had $20's and a soon to be $50, since all she had $50's, >no $20's, but did have $10's. >Clerk freaked, and said no way, and that she was not doing that! >Yes she was fresh out of high school. >I guess my expression reminded her of the one about making change for a $2 >bill. (there is no such thing as $2) >So she finally caught on... but the rest of the line went to another lane! > >ps. quite like the error in using whom. I'll bet there is not clerk that can >say, or spell, or use "whom" >http://web.ku.edu/~edit/whom.html > >> >>________________________________ >> >>From:Brian Oconnell <[email protected]> >>To: 'EMC-PSTC' <emc-pstc@using whom..ORG> >>Sent: Thursday, February 28, 2013 6:09 PM >>Subject: a CAB person and my Python >> >>CAB person - So back to this Python language thing? >>me - huh? >>CAB person - So how is the test data affected if you no longer write it all >>in C? >>me - none, the instrument just sees a command and responds, it never sees >>any elements of any programming language syntax. An ASCII string looks the >>same regardless of the language that was used to write the system. >>CAB person - How can the meters and source and logger and load not see the >>language? >>me - the equipment and the computer exchange serial streams of bit patterns >>that represent SCPI commands and data. The test equipment has no need to see >>any programming language, and has no ability to parse and no ability to >>interpret anything other than SCPI commands. >>CAB person - Whom is Skippy? >> >>Brian >> >>- >>---------------------------------------------------------------- >>This message is from the IEEE Product Safety Engineering Society emc-pstc >>discussion list. To post a message to the list, send your e-mail to >><[email protected]> >> >>All emc-pstc postings are archived and searchable on the web at: >>http://www.ieee-pses.org/emc-pstc.html >> >>Attachments are not permitted but the IEEE PSES Online Communities site at >>http://product-compliance.oc.ieee.org/ can be used for graphics (in well-used >>formats), large files, etc. >> >>Website: http://www.ieee-pses.org/ >>Instructions: http://listserv.ieee.org/request/user-guide.html >>List rules: http://www.ieee-pses.org/listrules.html >> >>For help, send mail to the list administrators: >>Scott Douglas <[email protected]> >>Mike Cantwell <[email protected]> >> >>For policy questions, send mail to: >>Jim Bacher: <[email protected]> >>David Heald: <[email protected]> >> >> >- >---------------------------------------------------------------- >This message is from the IEEE Product Safety Engineering Society emc-pstc >discussion list. To post a message to the list, send your e-mail to ><[email protected]> >All emc-pstc postings are archived and searchable on the web at: >http://www.ieee-pses.org/emc-pstc.html >Attachments are not permitted but the IEEE PSES Online Communities site at >http://product-compliance.oc.ieee.org/ can be used for graphics (in well-used >formats), large files, etc. >Website: http://www.ieee-pses.org/ >Instructions: http://listserv.ieee.org/request/user-guide.html >List rules: http://www.ieee-pses.org/listrules.html >For help, send mail to the list administrators: >Scott Douglas <[email protected]> >Mike Cantwell <[email protected]> >For policy questions, send mail to: >Jim Bacher <[email protected]> >David Heald <[email protected]> - >---------------------------------------------------------------- > >This message is from the IEEE Product Safety Engineering Society emc-pstc >discussion list. To post a message to the list, send your e-mail to ><[email protected]> >All emc-pstc postings are archived and searchable on the web at: >http://www.ieee-pses.org/emc-pstc.html >Attachments are not permitted but the IEEE PSES Online Communities site at >http://product-compliance.oc.ieee.org/ can be used for graphics (in well-used >formats), large files, etc. >Website: http://www.ieee-pses.org/ >Instructions: http://listserv.ieee.org/request/user-guide.html >List rules: http://www.ieee-pses.org/listrules.html >For help, send mail to the list administrators: >Scott Douglas <[email protected]> >Mike Cantwell <[email protected]> >For policy questions, send mail to: >Jim Bacher <[email protected]> >David Heald <[email protected]> > > - ---------------------------------------------------------------- This message is from the IEEE Product Safety Engineering Society emc-pstc discussion list. To post a message to the list, send your e-mail to <[email protected]> All emc-pstc postings are archived and searchable on the web at: http://www.ieee-pses.org/emc-pstc.html Attachments are not permitted but the IEEE PSES Online Communities site at http://product-compliance.oc.ieee.org/ can be used for graphics (in well-used formats), large files, etc. Website: http://www.ieee-pses.org/ Instructions: http://listserv.ieee.org/request/user-guide.html List rules: http://www.ieee-pses.org/listrules.html For help, send mail to the list administrators: Scott Douglas <[email protected]> Mike Cantwell <[email protected]> For policy questions, send mail to: Jim Bacher: <[email protected]> David Heald: <[email protected]>
