-
xkcd: Heartbleed Explanation
xkcd.com
Warning: this comic occasionally contains strong language (which may be unsuitable for children), unusual humor (which may be unsuitable for adults), ...
-
PythonLabs ~ Success Stories
python.pro.br
Python is in daily use in mission-critical applications at many leading-edge, high-growth enterprises. The language, associated tools and ...
-
Why Guido van Rossum supports the Ada Initiative, wears a "Python is for ...
adainitiative.org
The Ada Initiative has made record progress for women in open tech/culture in 2014. Now we ask you to donate before October 8th to support our ...
-
Dropbox - Listary - All your lists - Developer Blog
www.dropbox.com
A beautiful iOS app with shared datastores and local datastores.
-
Guido van Rossum on finding his way
medium.com
The Python creator and Dropbox engineer reflects on his early days in programming
-
Dropbox - New Datastore features! Shared datastores, local datastores, and ...
www.dropbox.com
Dropbox Developers - Build the power of Dropbox into your app. Your one-stop for the latest news on Dropbox's API platform
-
Dropbox - Swift apps with Dropbox - Developer Blog
www.dropbox.com
Learn how to use the Dropbox SDK in your Swift app.
-
I Liked Everything I Saw on Facebook for Two Days. Here's What It Did to ...
www.wired.com
I like everything. Or at least I did, for 48 hours. Literally everything Facebook sent my way, I liked---even if I hated it.
-
Dropbox - Debug your Dropbox app with app error logs - Developer Blog
www.dropbox.com
App error logs make it easy to debug Dropbox API calls.
-
Philip Guo - Python Tutor Live
pgbovine.net
I've been developing Online Python Tutor for the past 4.5 years, and it's been tremendously rewarding to see it being used by instructors and ...
-
The Philadelphia Python Users Group (PhillyPUG)
www.meetup.com
A Meetup group for the Philadelphia Python Users Group (PhillyPUG). Meet other Python programming language enthusiasts in the Philadelphia area. ...
-
Re: Python 3 is killing Python « python-list « ActiveState List Archives
code.activestate.com
© 2012 ActiveState Software Inc. All rights reserved. ActiveState®, Komodo®, ActivePerl®, ActivePython®, ActiveTcl®, and Stackato® are registered ...
-
Is Dropbox a bad place for women to work? Why or why not? - Quora
www.quora.com
Please confirm your email address. Resend Confirmation Link
-
Python is Now the Most Popular Introductory Teaching Language at Top U.S. ...
cacm.acm.org
Eight of the top 10 CS departments in the U.S., and ~70% of the top 40, teach Python in introductory courses.
-
Inside the Mirrortocracy
carlos.bueno.org
There's a problem with Silicon Valley and the subcultures that imitate it. It's a design bug woven into people's identities and sense of self-worth. ...
-
trollius 1.0.1 : Python Package Index
pypi.python.org
Port of the Tulip project (asyncio module, PEP 3156) on Python 2
-
Is Coding the New Literacy? | Mother Jones
www.motherjones.com
Why America's schools need to train a generation of hackers.
-
Python Datastore API - Dropbox
www.dropbox.com
The Datastore API enables you to sync your app's structured data. Datastore API syncs data quickly, manages conflicting changes, and even works ...
-
Dropbox - Core API - endpoint reference
www.dropbox.com
The Core API allows you to build the power of Dropbox directly into your app. It provides methods to read from and write to Dropbox, and powerful ...


--- layout: post title: Submitting commits to official Ruby & Rails documentation date: 2012-11-03 13:09:01.000000000 -07:00 type: post published: true status: publish categories: tags: [] meta: _edit_last: '1' _wp_old_slug: makjing-a-submit-to-the-official-ruby-docum author: login: admin email<EMAIL_ADDRESS>display_name: admin first_name: Carina C. last_name: Zon ---
Done! Submitted my very first commit for the official Ruby documentation.

— Carina C. Zona (@cczona) November 3, 2012
Patting myself on the back for having spotted the error. It was over 2 months old — surprising for a standard library like URI::HTTP. So I second-guessed myself initially.
Surely that doc gets scrutinized by hundreds of people daily. Surely someone else would have spotted it ages ago, if it were done incorrectly. Surely I just haven't heard about some fancy new syntactical construct. Surely the fact that the example doesn't work for me is because I must've done something incorrectly. Surely.
That voice in the back of the head is noise from imposter syndrome.
 A mythbuster, for me and for you:
$ cd ruby-official-repo
$ git log | grep -ic "typo"
842
Trust your instinct. Verify. Make better things happen. Commit.
Last month I also made a first commit for the official Rails documentation, and — hooray! — it was accepted. Though not without a brief facepalm moment when I accidentally submitted a big bunch of other people's commits with it. Luckily, the railsdocs repository is maintained separately from the Rails codebase. So it was a quick fix by doing git reset --HARD
on master branch then the documentation maintainers and I each did a git push -f
on our respective repos, and rebased my branch's commit back in. Voila, solved.
It's a good example of where Git is a big win for contributor, maintainers, and collaborators. It is also a good example of how wins like these are made easiest when developers are required to submit to an upstream via a branch rather than on top of master.
So, summary: I can now put "Rails documentation contributor" on the résumé, and hopefully soon will be able to put "Ruby documentation contributor" on it too. Don't worry; even though I'm a cool kid now, I still want to hang out with you.
UPDATE: Mission accomplished. What fun.
Documentation patch accepted. I'm officially a contributor to Ruby.Neato. bugs.ruby-lang.org/projects/ruby-…
— Carina C. Zona (@cczona) November 5, 2012


Bot Actions
Hello, I can help you if you reply with the following formats
Order Summary
Order ID, API Token
Check Item Price
Item ID, Item Location ID, Customer ID, API Token


Woman critically injured after collision between cement truck and car in Milton
by Bryann Aguilar, CP24.comOne person is in hospital in critical condition after a two-vehicle collision in Milton on Wednesday afternoon.
Emergency crews were called to 810 Nipissing Road, near Thompson Road North and Main Street East, just before 3:30 p.m. for reports of a crash.
Halton police said a cement truck and a car collided.
The female driver of the car, a 42-year-old Milton resident, had to be extricated by firefighters, police said. She was taken to a Hamilton hospital with life-threatening injuries. Her condition has been upgraded to serious but stable.
Police said the passenger of the car, a 15-year-old boy, was treated for minor injuries at the scene. An officer was taken to a local hospital after injuring his hands during the extrication.
The driver of the truck was not injured, police said.
The Collision Reconstruction Unit is investigating the crash.
Nipissing Road was closed in both directions for several hours but it has since reopened.
Investigators are requesting that anyone who witnessed the crash, or who may have stationary CCTV or dash-cam footage to please contact them.


DomDocument::html_dump_mem (PHP 4 >= 4.1.0) DomDocument::html_dump_mem — Dumps the internal XML tree back into a string as HTML 说明 string DomDocument::html_dump_mem ( void ) Creates an HTML document from the dom representation. This function usually is called after building a new dom document from scratch as in the example below. Example #1 Creating a simple HTML document header create_element("html"); $root = $doc->append_child($root); $head = $doc->create_element("head"); $head = $root->append_child($head); $title = $doc->create_element("title"); $title = $head->append_child($title); $text = $doc->create_text_node("This is the title"); $text = $title->append_child($text); echo $doc->html_dump_mem(); ?> 以上例程会输出：


--- layout: page title: Geräte tagline: selbstgebaute Klangobjekte permalink: /objekte/ images: - image_path: /assets/images/machines/klangobjekte_zusammen.jpg - image_path: /assets/images/machines/klangobjekt_gebaude.jpg - image_path: /assets/images/machines/klangobjekt_mp3.jpg - image_path: /assets/images/machines/klangobjekt_evelope2.jpg - image_path: /assets/images/machines/tumor_2.jpg - image_path: /assets/images/machines/cassette_2.jpg - image_path: /assets/images/machines/pilzstation_2.jpg - image_path: /assets/images/machines/synth_2.jpg title: Op Amp Synth - image_path: /assets/images/machines/machines.jpg title: Miscelanea - image_path: /assets/images/machines/amplifier.jpg title: Piezo-mic amplifier - image_path: /assets/images/machines/time_machine2.png - image_path: /assets/images/machines/soli.jpg ---


--- layout: page title: About header-img: "img/about-bg.png" ---
Welcome to my blog everyone :) I hope you find something of interest about my new adventure of becoming a Web Developer.


Line data Source code
1 : !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
2 : !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
3 : !!!!
4 : !!!! MIT License
5 : !!!!
6 : !!!! ParaMonte: plain powerful parallel Monte Carlo library.
7 : !!!!
8 : !!!! Copyright (C) 2012-present, The Computational Data Science Lab
9 : !!!!
10 : !!!! This file is part of the ParaMonte library.
11 : !!!!
12 : !!!! Permission is hereby granted, free of charge, to any person obtaining a
13 : !!!! copy of this software and associated documentation files (the "Software"),
14 : !!!! to deal in the Software without restriction, including without limitation
15 : !!!! the rights to use, copy, modify, merge, publish, distribute, sublicense,
16 : !!!! and/or sell copies of the Software, and to permit persons to whom the
17 : !!!! Software is furnished to do so, subject to the following conditions:
18 : !!!!
19 : !!!! The above copyright notice and this permission notice shall be
20 : !!!! included in all copies or substantial portions of the Software.
21 : !!!!
22 : !!!! THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
23 : !!!! EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
24 : !!!! MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.
25 : !!!! IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM,
26 : !!!! DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR
27 : !!!! OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE
28 : !!!! OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
29 : !!!!
30 : !!!! ACKNOWLEDGMENT
31 : !!!!
32 : !!!! ParaMonte is an honor-ware and its currency is acknowledgment and citations.
33 : !!!! As per the ParaMonte library license agreement terms, if you use any parts of
34 : !!!! this library for any purposes, kindly acknowledge the use of ParaMonte in your
35 : !!!! work (education/research/industry/development/...) by citing the ParaMonte
36 : !!!! library as described on this page:
37 : !!!!
38 : !!!! https://github.com/cdslaborg/paramonte/blob/main/ACKNOWLEDGMENT.md
39 : !!!!
40 : !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
41 : !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
42 :
43 : !> \brief This module contains classes and procedures for computing the date and time.
44 : !> \author Amir Shahmoradi
45 :
46 : module DateTime_mod
47 :
48 : implicit none
49 :
50 : public
51 : private :: queryDateTime
52 :
53 : character(*), parameter :: MODULE_NAME = "@DateTime_mod"
54 :
55 : !> The datetime_type class
56 : type, public :: DateTime_type
57 : character(8) :: date
58 : character(10) :: time
59 : character(5) :: zone
60 : integer :: Values(8)
61 : character(2) :: century
62 : character(4) :: year
63 : character(2) :: month
64 : character(2) :: day
65 : character(2) :: hour
66 : character(2) :: minute
67 : character(2) :: second
68 : character(3) :: millisecond
69 : character(21) :: fancyStyleBasic
70 : character(35) :: fancyStyle
71 : contains
72 : !> Query date and time.
73 : procedure, pass :: query => queryDateTime
74 : end type DateTime_type
75 :
76 : !%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
77 :
78 : contains
79 :
80 : !%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
81 :
82 : !> Function to query the [DateTime_type](@ref datetime_type) instance to the current time.
83 : !>
84 : !> @param[in,out] self : An object of [DateTime_type](@ref datetime_type) class.
85 395 : subroutine queryDateTime(self)
86 : #if INTEL_COMPILER_ENABLED && defined DLL_ENABLED && (OS_IS_WINDOWS || defined OS_IS_DARWIN)
87 : !DEC$ ATTRIBUTES DLLEXPORT :: queryDateTime
88 : #endif
89 : implicit none
90 : class(DateTime_type), intent(inout) :: self
91 : call date_and_time( date = self%date &
92 : , time = self%time &
93 : , zone = self%zone &
94 : , Values = self%Values &
95 395 : )
96 395 : self%century = self%date(1:2)
97 395 : self%year = self%date(1:4)
98 395 : self%month = self%date(5:6)
99 395 : self%day = self%date(7:8)
100 395 : self%hour = self%time(1:2)
101 395 : self%minute = self%time(3:4)
102 395 : self%second = self%time(5:6)
103 395 : self%millisecond = self%time(8:10)
104 : self%fancyStyleBasic = self%year // "/" // & ! 5 characters
105 : self%month // "/" // & ! 3 characters
106 : self%day //" - " // & ! 5 characters
107 : self%hour // ":" // & ! 3 characters
108 : self%minute // ":" // & ! 3 characters
109 395 : self%second ! 2 characters
110 : self%fancyStyle = self%fancyStyleBasic // "." // & ! basic+1 characters
111 : self%millisecond // " " // & ! 4 characters
112 395 : self%zone // " UTC" ! 9 characters
113 395 : end subroutine queryDateTime
114 :
115 : !%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
116 :
117 : !> Return date and time in a nice format.
118 : !>
119 : !> \return
120 : !> A character vector containing date and time in a nice format.
121 : !>
122 : !> \remark
123 : !> This is an impure function due to its dependence on `date_and_time()` Fortran intrinsic function.
124 437 : function getNiceDateTime() result(niceDateTime)
125 : #if INTEL_COMPILER_ENABLED && defined DLL_ENABLED && (OS_IS_WINDOWS || defined OS_IS_DARWIN)
126 : !DEC$ ATTRIBUTES DLLEXPORT :: getNiceDateTime
127 : #endif
128 : implicit none
129 : character(len=21) :: niceDateTime
130 : character(10) :: time
131 : character(8) :: date
132 437 : call date_and_time(date,time)
133 437 : niceDateTime = date(1:4)//'/'//date(5:6)//'/'//date(7:8)//' - '//time(1:2)//':'//time(3:4)//':'//time(5:6)
134 395 : end function getNiceDateTime
135 :
136 : !%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
137 :
138 : end module DateTime_mod ! LCOV_EXCL_LINE
|


Where to?
Maps
Our venues
Hack Cambridge is held in the Corn Exchange, and the Guildhall across the street. The main event will take place in the Corn Exchange, and workshops, demos, food, and the sleeping area will all be in the Guildhall. In any case, the location of events is always indicated in the timetable.
The Guildhall is just a few minutes' walk from the Corn Exchange, and the route will be well-signposted.
Volunteers will also show the way for each of the meals and workshops.
Getting to the venue
Information on how to get to the venue is on the dashboard.
To the dashboard


Version 0.2.2
This is a viewer for CityGML and CityJSON based on Ceisum. This project was generated with Angular CLI.
It aims to open and view models with the ability to:
Github Repository can be found here.
You may load your own model by clicking on the file button in the top right corner. If not, some examples can be loaded from the selection below.
CityJSON example file from the CityJSON example datasets.
CityGML example file containing sample data from the Noise ADE extension. Obtained from OpenGIS Schema Repository


This app contains a universal barcode scanning system that works on any type of platfrom with a camera including desktops, tablets, and phones. To run , simply allow access to your device camera and hold a barcode in front until the image is confirmed as captured.
I developed this website integrating device detection so that users would be directed to the appropriate app store depending on the device they are using.
My rebuild of the FlipBoard website using Javascript, HTML, CSS , and Jquery
Flash Card Guessing Game app using Ruby on Rails and Sinatra
This “ crowd-saving“ app helps lets individuals contribute and share in their savings goals. The app was developed using Ruby on Rails and incorporates the NexMo api.
(temporary login info -<EMAIL_ADDRESS>, p:password)
Simple game using vanilla JS, HTML and CSS
Water conservation and consumption awareness app. This app calculates every drop that water costs us and provides tips as to how one can conserve more
Web app that scrapes social media feeds for current address information to track food trucks in live-time . App uses Node.JS , JavaScript and the Etsy map API
This is the mobile interface I constructed using IonicJS that will eventually host the mobile version of this web app


Set the cookie name. By default XSRF-TOKEN is used as it is the expected name by AngularJS however other frameworks might use other names.
a new name for the cookie.
fluent
Set the cookie path. By default / is used.
a new path for the cookie.
fluent
Set the header name. By default X-XSRF-TOKEN is used as it is the expected name by AngularJS however other frameworks might use other names.
a new name for the header.
fluent
Should the handler give warning messages if this handler is used in other than https protocols?
true to nag
fluent
Set the body returned by the handler when the XSRF token is missing or invalid.
the body of the response. If null, no response body will be returned.
fluent
Set the timeout for tokens generated by the handler, by default it uses the default from the session handler.
token timeout
fluent
Instantiate a new CSRFHandlerImpl with a secret
CSRFHandler.create("s3cr37")
server secret to sign the token.
Generated using TypeDoc
This handler adds a CSRF token to requests which mutate state. In order change the state a (XSRF-TOKEN) cookie is set with a unique token, that is expected to be sent back in a (X-XSRF-TOKEN) header.
The behavior is to check the request body header and cookie for validity.
This Handler requires session support, thus should be added somewhere below Session and Body handlers.
Paulo Lopes


| Designed for use with JUnit and Ant. |
| Tests | Failures | Errors | Skipped | Success rate | Time |
|---|---|---|---|---|---|
| 81 | 24 | 57 | 0 | 0.00% | 6.188 |
| Note: failures are anticipated and checked for with assertions while errors are unanticipated. |
| Name | Tests | Errors | Failures | Skipped | Time(s) | Time Stamp | Host |
|---|---|---|---|---|---|---|---|
| com.ibatis.jpetstore.domain | 1 | 1 | 0 | 0 | 0.469 | 2017-07-28T12:39:44 | IRIS-VMQATest |
| com.ibatis.jpetstore.persistence | 24 | 0 | 24 | 0 | 1.453 | 2017-07-28T12:39:45 | IRIS-VMQATest |
| com.ibatis.jpetstore.presentation | 40 | 40 | 0 | 0 | 2.859 | 2017-07-28T12:39:50 | IRIS-VMQATest |
| com.ibatis.jpetstore.service | 16 | 16 | 0 | 0 | 1.407 | 2017-07-28T12:39:57 | IRIS-VMQATest |


To add or manage existing schedule, User has to select starting date and finishing date from the respective text boxes. Also, Schedule cannot be visible if User does not select Branch and Location. Once the Schedule is added, User can see User’s existing Schedule in the My Schedule panel. Also, in the action column in the My Schedule panel, the User has the option to add a Day which implies that User can add another day schedule.
Created with the Personal Edition of HelpNDoc: Free HTML Help documentation generator


File Transfer
Upload - Share - Download
Home
Help
About Us
Feedback Form
Uploads
Log Out
Loading image. Please wait
File Transfer
File Transfer
File Transfer
File Transfer
File Transfer
File Transfer
File Transfer
File Transfer
File Transfer
File Transfer
File Transfer
File Transfer
File Transfer
File Transfer
File Transfer


Document
{ "valueA": "Foo", "valueB": "Bar" }
Proof Field
Calculate Tree & Proof
Root Hash
Proof
Proof
Root Hash
Validate Proof
Proof


Stephen Ranger - Masters Thesis
Thesis Proposal
Thesis Proposal (PDF)
Thesis Final Draft (LaTeX to PDF)
Thesis Final Draft (LaTeX to PDF - Anonymous)
Thesis Updates
Thesis Update #1 - Octree, Icosatree, and Interactive Visualization
Thesis Update #2 - Data Structure Implementation and Processing
Thesis Update #3 - Level of Detail
Thesis Update #4 - Selection
Source Code Repositories (SVN) -- Read Only Access
Graphics API Library (http://www.stephenwranger.com/svn/graphics/)
Computational Geometry Library (http://www.stephenwranger.com/svn/compgeo/)
Thesis Library (http://www.stephenwranger.com/svn/thesis/)


|
liberis
|
Standard integer types. More...
Go to the source code of this file.
Typedefs | |
| typedef unsigned int | uint32_t |
| typedef unsigned short | uint16_t |
| typedef unsigned char | uint8_t |
| typedef signed int | int32_t |
| typedef signed short | int16_t |
| typedef signed char | int8_t |
| typedef volatile uint32_t | vuint32_t |
| typedef volatile uint16_t | vuint16_t |
| typedef volatile uint8_t | vuint8_t |
| typedef volatile int32_t | vint32_t |
| typedef volatile int16_t | vint16_t |
| typedef volatile int8_t | vint8_t |
| typedef uint32_t | u32 |
| typedef uint16_t | u16 |
| typedef uint8_t | u8 |
| typedef int32_t | s32 |
| typedef int16_t | s16 |
| typedef int8_t | s8 |
| typedef vuint32_t | vu32 |
| typedef vuint16_t | vu16 |
| typedef vuint8_t | vu8 |
| typedef vint32_t | vs32 |
| typedef vint16_t | vs16 |
| typedef vint8_t | vs8 |
Standard integer types.
| typedef signed short int16_t |
Signed 16bit integer
| typedef signed int int32_t |
Signed 32bit integer
| typedef signed char int8_t |
Signed 8bit integer
| typedef unsigned short uint16_t |
Unsigned 16bit integer
| typedef unsigned int uint32_t |
Unsigned 32bit integer
| typedef unsigned char uint8_t |
Unsigned 8bit integer


GHOST WORLD RATING: 9/10
For more reviews and movie scripts, visit http://www.joblo.com/
PLOT: After graduating from high school, two girl best friends try to figure out what they want to do with their lives. In the meantime, they make fun of people around them, attempt to get real jobs and play a dirty trick on an older, lonely guy. That being done, one of the girls gets a job, hoping to move on with her life, while the other, falls for the older, lonely guy, and starts hanging out with him more. Okay, so it doesn't sound all that exciting, but trust me...it's got some cool insight, great characters and a wonderful ambiance all around. See below...
CRITIQUE: There are great movies and then there are movies that hit you on a personal level and elevate it to an even greater level. Does that make any sense? Well, either way, I really loved this flick. It's not a "big movie" by any stretch of the imagination, but its characters, its environment, its authenticity and its capacity to capture the feeling of an outsider living in society today, well, really drew me into its story. A story which incidentally, doesn't have a typical structure. It's basically about these two high school girls who are trying to figure out what the next step in their lives will be. This leads to self-discovery, some introspection and an insightful look at the way people use facades in order to get by in life. Of course, you don't have to be a teenage girl to be able to relate to any of their feelings of alienation, concern for their futures, non-conformity and the general notion of not being able to "fit into" society (do you ever just feel trapped?). For many, there is a fine line between "putting food on the table" and "selling out".
I've personally always had a fascination with the so-called "weirdos" from high school (especially the goth chicks and girls with Doc Martens...yeah, baby!) Maybe because I was kinda weird myself (or maybe I still am...not sure). But the bottom line with most of these folks, as with the two girls in this film, is that they're basically just like the rest of us, but with some deeper insecurities, and a greater need to put up walls. The two ladies in this film put others down in order to feel better about their own stations in life and because they cannot seem to pursue their own goals. Of course, they don't do any of this consciously, but just like in real life (boy, do I ever know a lot of people like this!), it happens and it's interesting to watch them interact with the rest of the characters in this movie.
But don't let me make this film sound too profound! It's actually very funny, clever, extremely well-written and everyone in the cast fits their parts to a tee. Especially Buscemi and Birch, who are both perfect in their roles, and really give their respective characters the added layer of vulnerability needed to pull you in even further. I also appreciated the various plays on stereotypes in this film, but with a twist.   He doesn't pretend to be anything else. He's honest about it and that's what makes him that much more appealing. Birch's friend is also very typical of your know-it-all, sarcastic chickie-dee at the beginning of the film, but as their lives move forward, she grows, adapts and accepts some of what her life is offering, as opposed to Birch's character, who simply cannot seem to let go of her irresponsible teenage self.
Man, but there's so much more in here as well. There's drama, there's a genuine sense of empathy for the characters, there's an open-ended resolution that could not have been more ideal for a film as such, there are some nifty old-time tunes and there is an incredible feeling of loneliness woven deep within the film's fabric. Mind you, if you've read my entire review up to this point, you should also note that this is not your typical movie for your everyday moviegoer.  Anyway, as you can see, I really, really loved this movie, even more so because I'm quite confused about my own dinky future at this point in my life as well, so it likely struck a chord, or actually...several chords! Either way, check it out if you're looking for a sardonic flick with a unique point of view, some great performances, fun dialogue, a catchy soundtrack, many clever bits and a resounding, heart-felt message.
Where's JoBlo coming from? American Beauty (8/10) - Election (7/10) - Fight Club (10/10) - Ginger Snaps (8/10) - Happiness (3/10) - Magnolia (9/10) - Requiem for a Dream (8/10) - Rushmore (9/10) - Taxi Driver (10/10)
Review Date: August 29, 2001 Director: Terry Zwigoff Writers: Terry Zwigoff and Daniel Clowes Producers: John Malkovich, Lianne Halfon, Russell Smith Actors: Thora Birch as Enid Steve Buscemi as Seymour Scarlett Johansson as Rebecca Genre: Dramedy Year of Release: 2001 ------------------------------------ JoBlo's Movie Emporium http://www.joblo.com/ ------------------------------------ (c) 2001 Berge Garabedian
========== X-RAMR-ID: 29389 X-Language: en X-RT-ReviewID: 247300 X-RT-TitleID: 1109008 X-RT-SourceID: 573 X-RT-AuthorID: 1021 X-RT-RatingText: 9/10
The review above was posted to the
rec.arts.movies.reviews newsgroup (de.rec.film.kritiken for German reviews).
The Internet Movie Database accepts no responsibility for the contents of the
review and has no editorial control. Unless stated otherwise, the copyright
belongs to the author.
Please direct comments/criticisms of the review to relevant newsgroups.
Broken URLs inthe reviews are the responsibility of the author.
The formatting of the review is likely to differ from the original due
to ASCII to HTML conversion.
Related links: index of all rec.arts.movies.reviews reviews


This week as we were introduced to Arduino Uno and its software, we were provided to do certain tasks to familiarise ourselves with the software and the application of it.
Task 1: Write a program to blink the LED in a variety of patterns.
The equipment that I used were:
- USB Cable
- Breadboard
- Arduino Uno
- 1 LED (I used red)
- 3 jumper wires
- 1 220ohm resistor (red, red, brown stripes)
Setup Process
- Connect your components like the picture shown below:
- Connect your USB port to your device (laptop, computer, etc)
Coding Process
- Using the Arduino software, click on the open icon and upload the blink code under “01.Basics”
- From the code, setup the pins that you are using, I used pin 8 so my pin values are 8 here:
- After that, input the time value you want for the LED to on and off. In the software, we use milliseconds. One second is equals to 1000 milliseconds.
- Here, the LED should turn on for one second and off for one second.
- Play around with the time values. For the second timing, I made the intervals shorter as shown here below:
Task 2: Controlling 2 LEDs using a switch
Continuing on from task 1, add on these components:
- 3 jumper wires
- 1 220ohm resistor
- 1 1kiloohm resistor (orange, black, brown stripes)
- Different coloured LED (I used green)
- Pushbutton Switch
- Connect in the same arrangement as the previous one just using a different pin. For me, I used pin 7.
- Connect the rest of your components to the picture shown below:
- I used pin 6 for the pushbutton switch
- Connect your last jumper wire from the same column as your pushbutton switch to ground in your breadboard
Coding Process
- You need to setup your constant functions as in those that will not change. This will help you to code easier by using those function names.
- In this case, the button will be the one reading thus it should be INPUT whereas for the LEDs, there would be the outputs.
- “state = 0” means that we are assigning a value of 0 to the function “state”
- I am using state to show what I want to happen in different cases.
- Case 0: LEDred is off, LEDgreen is off as well
- (Press)
- Case 1: LEDred is on, LEDgreen is off
- (Press)
- Case 2: LEDred is off, LEDgreen is on
- (Press)
- Case 3: LEDred and LEDgreen is on
- (Press-> goes back to Case 0)
Task 3: Flashing LEDs using switch
Demonstration
Challenges
I had a hard time trying to figure out the code on my own for the switch control part of the assignment. However, after asking for my teacher’s help, I learnt a lot of new things like how to use the state function to execute a sequence of cases. One challenge I also faced was that every time I pressed the button, it would jump and execute the next case even though it had not executed the previous one. This is called bouncing: It is when two metal parts come into contact to short the supply. This thus creates a false triggering or multiple triggering like the button is pressed multiple times.
Using a Potentiometer (Variable Resistor) to control the brightness of an LED
Components you will need:
- Arduino UNO
- 1 breadboard
- 1 LED (I used red)
- 1 Potentiometer
- 1 220ohm resistor
- 7 jumper wires
Set-up process
- Set-up a simple LED control on one side (refer to the first task)
- Place the potentiometer and connect the left pin to the positive side of the breadboard (VCC)
- Connect the middle pin to the analog pin A0
- Connect the right pin to the ground; negative side of the breadboard
Coding process


We optimize cats!
- cultivate integrated markets
- integrate global niches
- redefine interactive web-readiness
- enhance mission-critical niches
- revolutionize robust systems
- engage B2B systems
- exploit end-to-end e-commerce
- syndicate vertical portals
- target 24/7 mindshare
- strategize world-class infomediaries
- transform world-class mindshare
- disintermediate robust networks
- empower customized e-tailers
- architect cross-platform networks


MediaTek LinkIt Connect 7681
This example shows you how to build an application that lets you contrle the leds on the MediaTek LinkIt Connect 7681 development board using TCP-sockets.
Source code
You can browse the source code for this example at the Evothings GitHub repository
The file index.html contains the HTML markup of the app and the buisness logic is placed in the app.js
The patch that you need to apply to the SDK fetched from MediaTek can be found here.
What you need
This example runs in Evothings Viewer on Android or iOS.
You need an iOS or Android device as well as a LinkIt Connect 7681 from MediaTek.
You also need a computer running Microsoft Windows or Ubuntu.
How to get up and running
Follow these steps to get started with this example:
- Install the software development kit (1.71) provided by MediaTek, how to do that can be found in their Developer's guide.
- Copy the Evothings-MediaTek-Connect-7681-TCP-Led.patch to the path and execute the following command: patch -p1 < Evothings-MediaTek-Connect-7681-TCP-Led.patch
- Open the file cust/iot_custom.c and find the function IoT_Cust_SM_Smnt(). Change the Ssid variable to the name of your network and the Passphrase to the password of named network.
- Open a serial connection to the board and note the IP address och the board.
- Run Evothings Workbench on your computer.
- Connect to the Workbench from Evothings Viewer.
- Run the "MediaTek LinkIt Connect 7681" example from the Workbench window.
- Connect to your development board using the IP address noted in previous step.


I was born in Ridgecrest, CA in 1988. When I was young my father was in the Navy so we moved quite a bit. I've lived in four states:
I studied Communication at Portland State University, and am currently practicing to become a professional web developer. In my free time you can often find me watching (or even better, attending) NBA games, hanging out with my girlfriend, or watching movies.


1 Equipment Details
2 Shipping Details
3 Submission
Shipping List *
MODEL *
MANUFACTURER *
QUANTITY *
SERIAL NUMBERS
Supported Documents
Additional Information


Ubiquitious Language - 'Software Architect's Handbook'
Ubiquitous Language and the imortance of just agreeing on what to call things.
Ubiquitous Language
Ubiquitous language might not seem like the flashiest thing to pul out of a software architecture book, but I have found that clearly communicating software requirements has been the distinguishing factor of recent projects I have worked on.
To take a step back, a peice of software is only useful in the way it performs some task (or helps a human perform a task). The details for how it gets that task done are not nearly as important as the simple question: does the software do what it needs to do. Within a business, ‘thing’ the program needs to do is often determined in part business owners, and business owners don’t always speak the language as the developers. One solution to this problem is to create a ubiquitous language: a common language all team members and stakeholders agree upon to refer to parts of the domain.
Take a recent project I worked on as an example. My team was tasked with creating what our product team referred to as a ‘subscription model’ for students. Unlike many models, the payments made by the students would not follow a monthly cadence, but rather be billed to each student by their school semester. Moreover, the students would not be paying for indefintely for continued access, but rather just a set number of times before they ‘owned’ the product. Does that sound like a ‘subscription’? No. No it is not so much a subscription as a payment broken into a series of installments, and it took our engineering team a long time (weeks!) to reconcile that this ‘subscription’ was really a payment quantity split into irregular installments.
This miscommunication went both ways - internally, or engineering team referred to these payment periods as ‘semesters’ as to us, each payment period aligned with a school semester. This colloquial usage led us to name our models, routes, and text within pages as ‘semesters’. It wasn’t until we met a month or so later with our training team (responsible with educating school-personel about our software) that we realized the err of our ways - ‘semesters’ is not the term all schools use to descibe their course run times. Moreover, our ‘payment periods’ would not always line up with these ‘semesters’ or course blocks. Long story short, we needed to rename all our end-user facing terminology, but we still had all the dangling references to the term ‘semester’.
All of this may have been avoided if we had just agreed on what we would call things from the start while we - A ubiquitious language.


---
layout: post
authors: ["Greg Wilson"]
title: First Round at Lawrence Berkeley
date: 2013-03-05
time: "09:00:00"
tags: ["Lawrence Berkeley National Laboratory"]
---
We just wrapped up a two-day workshop at the Lawrence Berkeley National Laboratory, and another is due to start tomorrow. Here's what worked and what didn't from the first one:
| Good |
Bad |
- Doing examples ourselves
- Liked Python examples
- Interactive
- Greg kinda knows this stuff
- Like the history lessons etc.
- Went through a lot of things
- Liked IPython Notebook
- Like intro to Git
- Intro to shell
- Examples are incremental
- Good mix of theory and hands-on
- Sticky notes
- Everything is open source
- Liked keeping functions small
- Liked red-green-refactor
|
- Little more structure please
- Lost with how to use Git
- Wanted a cheat sheet
- Wanted more Python
- Not a break Monday aft.
- Not clear how to apply all tips to all things
- Wanted more structure Monday aft. (and I was teaching it)
- Wanted cookies in the afternoon
- Too many things at once
- Poor choice of room
- Need a book or handouts
- Didn't see Python interact with R and MATLAB
- More specific to specific groups
- Bringing Python back to the shell etc.
- How to save terminal session/notebook/etc.
|
Many thanks to Shreyas Cholia, Adam Stone, Nina Lucido, Geoff Oxberry, Matthew Brett, Paul Ivanov, and all our learners for making it a success.


@examples This example creates a new character array using both string and Unicode values then displays them.
Public Sub Main() Dim Chars() As Integer Dim Char As Variant Chars = NewChars("a", "b", 99, 100) Debug.Print "The set of characters." For Each Char In Chars Debug.Print CorString.Format("{0,3} = ""{0:$}""", Char) Next End Sub ' This example code produces the following output. ' ' The set of characters. ' 97 = "a" ' 98 = "b" ' 99 = "c" ' 100 = "d"


Weather Dashboard ☀☁
Check Weather Conditions:
Enter your desired city above.
Search
Currently:
Next Five Days:


--- layout: plainarticle title: Homecoming 2018 - General Assembly - Live stream permalink: /livestream/ --- {% include iframe.html src='https://livestream.com/accounts/7600301/events/8377010/player?width=640&height=360&enableInfoAndActivity=true&defaultDrawer=&autoPlay=true&mute=false' %}
If the embedded live stream does not work for you, please go to https://livestream.com/accounts/7600301/events/8377010.


MIT Calendar
Friday, February 15, 2008
Today's events
Today's exhibits
Academic calendar
MIT holidays
Browse events by category
in the next 7 days
in the next 15 days
in the next 30 days
in the past 15 days
in the past 30 days
this school term
this school year


There are some places where we make specific references to the location of Soar, Tcl, or the TSI, or to a specific version of one of these.† Below is a list of those places so a user who chooses to install in some alternate directory structure can change the references to make things work.† Also, cases where a different version may also work (i.e. a newer version of the TSI) are listed.† This list is probably only partial.
1) soar-8.3.5
a. SoarInterface VC++ project
i. Links to tcl83.dll
1. May want to use a different version of Tcl
b. start-soar.tcl
i. set tsi_library† [file join [file join [pwd] ..] tsi-3.1.5]
1. May want to specify a different version of the TSI here
c. Desktop/programs shortcuts
i. assume wish.exe exists in C:\Tcl\bin
1. Tcl may be installed elsewhere
2. May not have wish.exe (i.e. may have wish83.exe)
d. Tsi-3.1.5
i. $name eval {package require Tk}
1. this line may not work with some Tcl installs or versions
a. error message says canít find package Tk
2. can replace with one of the following (should be in file, commented out)
a. load tk83.dll Tk $name
b. load {} Tk $name
2) soar-8.4.5
a. SoarInterface VC++ project
i. Links to tcl83.dll
1. May want to use a different version of Tcl
b. start-soar.tcl
i. set tsi_library† [file join [file join [pwd] ..] tsi-3.1.5]
1. May want to specify a different version of the TSI here
c. Desktop/programs shortcuts
i. assume wish.exe exists in C:\Tcl\bin
1. Tcl may be installed elsewhere
2. May not have wish.exe (i.e. may have wish83.exe)
3) sgio-1.0.5
a. InstallShield Installer
i. Sets user environment variable TCL_LIBRARY = C:\Tcl\lib\tcl8.3
1. Tcl may be installed elsewhere
2. May want to use a different version of Tcl
3. May want to set a system variable so it works for all users
4. NOTE: It is not understood why this variable is required (it isnít required for any of the other packages)
b. Shared VC++ project
i. Additional include directory: c:\Tcl\include
1. Tcl may be installed elsewhere
c. Soarside VC++ project
i. Links to tcl83.dll and tk83.dll
1. May want to use a different version of Tcl
ii. Additional include directory: c:\Tcl\include
1. Tcl may be installed elsewhere
iii. Additional library path: C:\Tcl\lib\
1. Tcl may be installed elsewhere
iv. Program arguments (for launching from within Visual Studio)
1. May have to change to reflect desired port number and init file name and path
d. Simside VC++ project
i. Additional include directory: ..\..\soar-8.4.5\kernel
1. May want to compile with files from a different version of Soar
4) eaters-3.0.5
a. start-eaters.tcl
i. set soar_library [file join [file join [pwd] ..] [file join "soar-8.3.5" "library"]]
1. Notice the directory is relative to the eaters dir
a. May want to specify an absolute path, i.e. if located on a different drive or directory tree
2. May want to specify a different version of Soar here
ii. set tsi_library† [file join [file join [pwd] ..] tsi-3.1.5]
1. Notice the directory is relative to the eaters dir
a. May want to specify an absolute path, i.e. if located on a different drive or directory tree
2. May want to specify a different version of the TSI here
b. Desktop/programs shortcuts
i. assume wish.exe exists in C:\Tcl\bin
1. Tcl may be installed elsewhere
2. May not have wish.exe (i.e. may have wish83.exe)
5) tanksoar-3.0.5
a. start-tanksoar.tcl
i. set soar_library [file join [pwd] [file join .. [file join "soar-8.3.5" "library"]]]
1. Notice the directory is relative to the tanksoar dir
a. May want to specify an absolute path, i.e. if located on a different drive or directory tree
2. May want to specify a different version of Soar here
ii. set tsi_library [file join [pwd] [file join .. "tsi-3.1.5"]]
1. Notice the directory is relative to the tanksoar dir
a. May want to specify an absolute path, i.e. if located on a different drive or directory tree
2. May want to specify a different version of the TSI here
b. Desktop/programs shortcuts
i. assume wish.exe exists in C:\Tcl\bin
1. Tcl may be installed elsewhere
2. May not have wish.exe (i.e. may have wish83.exe)


PacketCollector
and StanzaListener
instances to filter for stanzas with particular attributes.See: Description
| Interface | Description |
|---|---|
| PacketFilter | Deprecated
use
StanzaFilter |
| StanzaFilter |
Defines a way to filter stanzas for particular attributes.
|
| Class | Description |
|---|---|
| AbstractListFilter | |
| AndFilter |
Implements the logical AND operation over two or more stanza(/packet) filters.
|
| FlexibleStanzaTypeFilter<S extends Stanza> |
Filters for stanzas of a particular type and allows a custom method to further filter the packets.
|
| FromMatchesFilter |
Filter for packets where the "from" field exactly matches a specified JID.
|
| IQReplyFilter |
Filters for packets which are a valid reply to an IQ request.
|
| IQResultReplyFilter | |
| IQTypeFilter |
A filter for IQ stanza(/packet) types.
|
| MessageTypeFilter |
Filters for packets of a specific type of Message (e.g.
|
| MessageWithBodiesFilter |
Filters message stanzas which have at least one body.
|
| MessageWithSubjectFilter |
Filters message stanzas which have at least one body.
|
| NotFilter |
Implements the logical NOT operation on a stanza(/packet) filter.
|
| OrFilter |
Implements the logical OR operation over two or more stanza(/packet) filters.
|
| PacketExtensionFilter | Deprecated
use
StanzaExtensionFilter instead. |
| PacketIDFilter | Deprecated
use
StanzaIdFilter instead. |
| PacketTypeFilter | Deprecated
use
StanzaTypeFilter instead. |
| PresenceTypeFilter |
A filter for Presence types.
|
| StanzaExtensionFilter |
Filters for stanzas with a particular type of stanza extension.
|
| StanzaIdFilter |
Filters for Stanzas with a particular stanza ID.
|
| StanzaTypeFilter |
Filters for Stanzas of a particular type.
|
| ThreadFilter |
Filters for message packets with a particular thread value.
|
| ToFilter |
PacketCollector
and StanzaListener
instances to filter for stanzas with particular attributes.


Numbers 10:28
Thus were the journeyings of the children of Israel according to their armies, when they set forward.


Home
About
Contact
Home
About
Contact
menu
Coming really soon!
If you would like to be informed when the big day comes,
please share you e-mail address below.
share
Need to Connect with Art people?
Join Us!
Here
Fill in the form & join our beloved community or artists and art lovers.
We'll take care of the rest.


{% comment %} # # Displays an image inside a post. # The image must be located in /assets/img/posts/ # # Use: {% include posts.html src="image.jpg" alt="Description" %} # {% endcomment %} {% assign src = '/assets/img/posts/' | append: include.src %}


Why join the numbers?
New GameHow to play: Use your arrow keys to move the tiles. When two tiles touch, they merge into one!
How to win: You must learn to see the game's true nature, and see that it is emptiness.
Note: This is a trivial fork (with source on GitHub) of the official version of 2048, which you can play via http://git.io/2048.
Created by Eric Hansander. Based on 2048 by Gabriele Cirulli, which in turn is "based on 1024 by Veewo Studio and conceptually similar to Threes by Asher Vollmer."


HOSTNAME field of the Syslog message as defined in RFC 5424 - The
Syslog Protocol.
The HOSTNAME field identifies the machine that originally sent the
syslog message.
The HOSTNAME field SHOULD contain the hostname and the domain name of
the originator in the format specified in STD 13 [RFC1034]. This
format is called a Fully Qualified Domain Name (FQDN) in this
document.
In practice, not all syslog applications are able to provide an FQDN.
As such, other values MAY also be present in HOSTNAME. This document
makes provisions for using other values in such situations. A syslog
application SHOULD provide the most specific available value first.
The order of preference for the contents of the HOSTNAME field is as
follows:
1. FQDN
2. Static IP address
3. hostname
4. Dynamic IP address
5. the NILVALUE
If an IPv4 address is used, it MUST be in the format of the dotted
decimal notation as used in STD 13 [RFC1035]. If an IPv6 address is
used, a valid textual representation as described in [RFC4291],
Section 2.2, MUST be used.
Syslog applications SHOULD consistently use the same value in the
HOSTNAME field for as long as possible.
The NILVALUE SHOULD only be used when the syslog application has no
way to obtain its real hostname. This situation is considered highly
unlikely.


Super Junior's Shindong reveals his weight loss and a slimmer jaw line in new Instagram post
by sl278Super Junior's Shindong has revealed his weight loss.
The popular star uploaded a video on his personal Instagram on November 21st that showed off his slimmer jawline with a simple caption stating: "good morning". He is seen receiving hairstyling while maneuvering the camera to show off his slimmer face.
Netizens have been cheering him on as he pursues better health, saying:
"So handsome."
"Cutie."
"Keep it up!"
Shindong is currently appearing in the web reality show 'Analog Trip'.


Here's a list of all control commands and a description, what they do:
.A16
Valid only in 65816 mode. Switch the accumulator to 16 bit.
Note: This command will not emit any code, it will tell the assembler to create 16 bit operands for immediate accumulator addressing mode.
See also:
.SMART
.A8
Valid only in 65816 mode. Switch the accumulator to 8 bit.
Note: This command will not emit any code, it will tell the assembler to create 8 bit operands for immediate accu addressing mode.
See also:
.SMART
.ADDR
Define word sized data. In 6502 mode, this is an alias for .WORD
and
may be used for better readability if the data words are address values. In
65816 mode, the address is forced to be 16 bit wide to fit into the current
segment. See also
.FARADDR
. The command
must be followed by a sequence of (not necessarily constant) expressions.
Example:
.addr $0D00, $AF13, _Clear
.ALIGN
Align data to a given boundary. The command expects a constant integer argument that must be a power of two, plus an optional second argument in byte range. If there is a second argument, it is used as fill value, otherwise the value defined in the linker configuration file is used (the default for this value is zero).
Since alignment depends on the base address of the module, you must give the same (or a greater) alignment for the segment when linking. The linker will give you a warning, if you don't do that.
Example:
.align 256
.ASCIIZ
Define a string with a trailing zero.
Example:
Msg: .asciiz "Hello world"
This will put the string "Hello world" followed by a binary zero into the current segment. There may be more strings separated by commas, but the binary zero is only appended once (after the last one).
.ASSERT
Add an assertion. The command is followed by an expression, an action
specifier, and an optional message that is output in case the assertion
fails. If no message was given, the string "Assertion failed" is used. The
action specifier may be one of warning
or error
. The assertion is
evaluated by the assembler if possible, and also passed to the linker in the
object file (if one is generated). The linker will then evaluate the
expression when segment placement has been done.
Example:
.assert * = $8000, error, "Code not at $8000"
The example assertion will check that the current location is at $8000,
when the output file is written, and abort with an error if this is not
the case.  The action specifier
warning
outputs a warning, while the error
specifier outputs
an error message. In the latter case, generation of the output file is
suppressed in both the assembler and linker.
.AUTOIMPORT
Is followed by a plus or a minus character. When switched on (using a +), undefined symbols are automatically marked as import instead of giving errors. When switched off (which is the default so this does not make much sense), this does not happen and an error message is displayed. The state of the autoimport flag is evaluated when the complete source was translated, before outputting actual code, so it is not possible to switch this feature on or off for separate sections of code. The last setting is used for all symbols.
You should probably not use this switch because it delays error messages about undefined symbols until the link stage. The cc65 compiler (which is supposed to produce correct assembler code in all circumstances, something which is not true for most assembler programmers) will insert this command to avoid importing each and every routine from the runtime library.
Example:
.autoimport + ; Switch on auto import
.BANKBYTES
Define byte sized data by extracting only the bank byte (that is, bits 16-23) from
each expression. This is equivalent to
.BYTE
with
the operator '^' prepended to each expression in its list.
Example:
.define MyTable TableItem0, TableItem1, TableItem2, TableItem3
TableLookupLo: .lobytes MyTable
TableLookupHi: .hibytes MyTable
TableLookupBank: .bankbytes MyTable
which is equivalent to
TableLookupLo: .byte <TableItem0, <TableItem1, <TableItem2, <TableItem3
TableLookupHi: .byte >TableItem0, >TableItem1, >TableItem2, >TableItem3
TableLookupBank: .byte ^TableItem0, ^TableItem1, ^TableItem2, ^TableItem3
See also:
.BYTE
,
.HIBYTES
,
.LOBYTES
.BSS
Switch to the BSS segment. The name of the BSS segment is always "BSS", so this is a shortcut for
.segment "BSS"
See also the
.SEGMENT
command.
.BYT, .BYTE
Define byte sized data. Must be followed by a sequence of (byte ranged) expressions or strings.
Example:
.byte "Hello "
.byt "world", $0D, $00
.CASE
Switch on or off case sensitivity on identifiers. The default is off (that is, identifiers are case sensitive), but may be changed by the -i switch on the command line. The command must be followed by a '+' or '-' character to switch the option on or off respectively.
Example:
.case - ; Identifiers are not case sensitive
.CHARMAP
Apply a custom mapping for characters. The command is followed by two
numbers in the range 1..255. The first one is the index of the source
character, the second one is the mapping. The mapping applies to all
character and string constants when they generate output, and overrides
a mapping table specified with the
-t
command line switch.
Example:
.charmap $41, $61 ; Map 'A' to 'a'
.CODE
Switch to the CODE segment. The name of the CODE segment is always "CODE", so this is a shortcut for
.segment "CODE"
See also the
.SEGMENT
command.
.CONDES
Export a symbol and mark it in a special way. The linker is able to build tables of all such symbols. This may be used to automatically create a list of functions needed to initialize linked library modules.
Note: The linker has a feature to build a table of marked routines, but it
is your code that must call these routines, so just declaring a symbol with
.CONDES
does nothing by itself.
All symbols are exported as an absolute (16 bit) symbol. You don't need to
use an additional
.EXPORT
statement, this
is implied by .CONDES
.
.CONDES
is followed by the type, which may be constructor
,
destructor
or a numeric value between 0 and 6 (where 0 is the same as
specifying constructor
and 1 is equal to specifying destructor
).
The
.CONSTRUCTOR
,
.DESTRUCTOR
and
.INTERRUPTOR
commands are actually shortcuts for .CONDES
with a type of constructor
resp. destructor
or interruptor
.
After the type, an optional priority may be specified. Higher numeric values mean higher priority. If no priority is given, the default priority of 7 is used. Be careful when assigning priorities to your own module constructors so they won't interfere with the ones in the cc65 library.
Example:
.condes ModuleInit, constructor
.condes ModInit, 0, 16
See the
.CONSTRUCTOR
,
.DESTRUCTOR
and
.INTERRUPTOR
commands and the separate section
Module constructors/destructors explaining the feature in more
detail.
.CONSTRUCTOR
Export a symbol and mark it as a module constructor. This may be used together with the linker to build a table of constructor subroutines that are called by the startup code.
Note: The linker has a feature to build a table of marked routines, but it is your code that must call these routines, so just declaring a symbol as constructor does nothing by itself.
A constructor is always exported as an absolute (16 bit) symbol. You don't
need to use an additional .export
statement, this is implied by
.constructor
. It may have an optional priority that is separated by a
comma. Higher numeric values mean a higher priority. If no priority is
given, the default priority of 7 is used. Be careful when assigning
priorities to your own module constructors so they won't interfere with the
ones in the cc65 library.
Example:
.constructor ModuleInit
.constructor ModInit, 16
See the
.CONDES
and
.DESTRUCTOR
commands and the separate section
Module constructors/destructors explaining the
feature in more detail.
.DATA
Switch to the DATA segment. The name of the DATA segment is always "DATA", so this is a shortcut for
.segment "DATA"
See also the
.SEGMENT
command.
.DBYT
Define word sized data with the hi and lo bytes swapped (use .WORD
to
create word sized data in native 65XX format). Must be followed by a
sequence of (word ranged) expressions.
Example:
.dbyt $1234, $4512
This will emit the bytes
$12 $34 $45 $12
into the current segment in that order.
.DEBUGINFO
Switch on or off debug info generation. The default is off (that is, the object file will not contain debug infos), but may be changed by the -g switch on the command line. The command must be followed by a '+' or '-' character to switch the option on or off respectively.
Example:
.debuginfo + ; Generate debug info
.DEFINE
Start a define style macro definition. The command is followed by an identifier (the macro name) and optionally by a list of formal arguments in braces. See section Macros.
.DEF, .DEFINED
Builtin function. The function expects an identifier as argument in braces.
The argument is evaluated, and the function yields "true" if the identifier
is a symbol that is already defined somewhere in the source file up to the
current position. Otherwise the function yields false. As an example, the
.IFDEF
statement may be replaced by
.if .defined(a)
.DESTRUCTOR
Export a symbol and mark it as a module destructor. This may be used together with the linker to build a table of destructor subroutines that are called by the startup code.
Note: The linker has a feature to build a table of marked routines, but it is your code that must call these routines, so just declaring a symbol as constructor does nothing by itself.
A destructor is always exported as an absolute (16 bit) symbol. You don't
need to use an additional .export
statement, this is implied by
.destructor
. It may have an optional priority that is separated by a
comma. Higher numerical values mean a higher priority. If no priority is
given, the default priority of 7 is used. Be careful when assigning
priorities to your own module destructors so they won't interfere with the
ones in the cc65 library.
Example:
.destructor ModuleDone
.destructor ModDone, 16
See the
.CONDES
and
.CONSTRUCTOR
commands and the separate
section
Module constructors/destructors explaining
the feature in more detail.
.DWORD
Define dword sized data (4 bytes) Must be followed by a sequence of expressions.
Example:
.dword $12344512, $12FA489
.ELSE
Conditional assembly: Reverse the current condition.
.ELSEIF
Conditional assembly: Reverse current condition and test a new one.
.END
Forced end of assembly. Assembly stops at this point, even if the command is read from an include file.
.ENDENUM
End a
.ENUM
declaration.
.ENDIF
Conditional assembly: Close a
.IF...
or
.ELSE
branch.
.ENDMAC, .ENDMACRO
End of macro definition (see section Macros).
.ENDPROC
End of local lexical level (see
.PROC
).
.ENDREP, .ENDREPEAT
End a
.REPEAT
block.
.ENDSCOPE
End of local lexical level (see
.SCOPE
).
.ENDSTRUCT
Ends a struct definition. See the
.STRUCT
command and the separate section named
"Structs and unions".
.ENUM
Start an enumeration. This directive is very similar to the C enum
keyword. If a name is given, a new scope is created for the enumeration,
otherwise the enumeration members are placed in the enclosing scope.
In the enumeration body, symbols are declared. The first symbol has a value of zero, and each following symbol will get the value of the preceding plus one. This behaviour may be overridden by an explicit assignment. Two symbols may have the same value.
Example:
.enum errorcodes
no_error
file_error
parse_error
.endenum
Above example will create a new scope named errorcodes
with three
symbols in it that get the values 0, 1 and 2 respectively. Another way
to write this would have been:
.scope errorcodes
no_error = 0
file_error = 1
parse_error = 2
.endscope
Please note that explicit scoping must be used to access the identifiers:
.word errorcodes::no_error
A more complex example:
.enum
EUNKNOWN = -1
EOK
EFILE
EBUSY
EAGAIN
EWOULDBLOCK = EAGAIN
.endenum
In this example, the enumeration does not have a name, which means that the
members will be visible in the enclosing scope and can be used in this scope
without explicit scoping. The first member (EUNKNOWN
) has the value -1.
The value for the following members is incremented by one, so EOK
would
be zero and so on. EWOULDBLOCK
is an alias for EGAIN
, so it has an
override for the value using an already defined symbol.
.ERROR
Force an assembly error. The assembler will output an error message preceded by "User error" and will not produce an object file.
This command may be used to check for initial conditions that must be set before assembling a source file.
Example:
.if foo = 1
...
.elseif bar = 1
...
.else
.error "Must define foo or bar!"
.endif
See also the
.WARNING
and
.OUT
directives.
.EXITMAC, .EXITMACRO
Abort a macro expansion immediately. This command is often useful in recursive macros. See separate section Macros.
.EXPORT
Make symbols accessible from other modules. Must be followed by a comma separated list of symbols to export, with each one optionally followed by an address specification and (also optional) an assignment. Using an additional assignment in the export statement allows to define and export a symbol in one statement. The default is to export the symbol with the address size it actually has. The assembler will issue a warning, if the symbol is exported with an address size smaller than the actual address size.
Examples:
.export foo
.export bar: far
.export foobar: far = foo * bar
.export baz := foobar, zap: far = baz - bar
As with constant definitions, using :=
instead of =
marks the
symbols as a label.
See:
.EXPORTZP
.EXPORTZP
Make symbols accessible from other modules. Must be followed by a comma
separated list of symbols to export. The exported symbols are explicitly
marked as zero page symbols. An assignment may be included in the
.EXPORTZP
statement. This allows to define and export a symbol in one
statement.
Examples:
.exportzp foo, bar
.exportzp baz := $02
See:
.EXPORT
.FARADDR
Define far (24 bit) address data. The command must be followed by a sequence of (not necessarily constant) expressions.
Example:
.faraddr DrawCircle, DrawRectangle, DrawHexagon
See:
.ADDR
.FEATURE
This directive may be used to enable one or more compatibility features
of the assembler. While the use of .FEATURE
should be avoided when
possible, it may be useful when porting sources written for other
assemblers. There is no way to switch a feature off, once you have
enabled it, so using
.FEATURE xxx
will enable the feature until end of assembly is reached.
The following features are available:
at_in_identifiers
Accept the at character (`@') as a valid character in identifiers. The at character is not allowed to start an identifier, even with this feature enabled.
c_comments
Allow C like comments using /*
and */
as left and right
comment terminators. Note that C comments may not be nested. There's also a
pitfall when using C like comments: All statements must be terminated by
"end-of-line". Using C like comments, it is possible to hide the newline,
which results in error messages. See the following non working example:
lda #$00 /* This comment hides the newline
*/ sta $82
dollar_in_identifiers
Accept the dollar sign (`$') as a valid character in identifiers. The dollar character is not allowed to start an identifier, even with this feature enabled.
dollar_is_pc
The dollar sign may be used as an alias for the star (`*'), which gives the value of the current PC in expressions. Note: Assignment to the pseudo variable is not allowed.
labels_without_colons
Allow labels without a trailing colon. These labels are only accepted, if they start at the beginning of a line (no leading white space).
leading_dot_in_identifiers
Accept the dot (`.') as the first character of an identifier. This may be used for example to create macro names that start with a dot emulating control directives of other assemblers. Note however, that none of the reserved keywords built into the assembler, that starts with a dot, may be overridden. When using this feature, you may also get into trouble if later versions of the assembler define new keywords starting with a dot.
loose_char_term
Accept single quotes as well as double quotes as terminators for char constants.
loose_string_term
Accept single quotes as well as double quotes as terminators for string constants.
missing_char_term
Accept single quoted character constants where the terminating quote is missing.
lda #'a
Note: This does not work in conjunction with .FEATURE
loose_string_term
, since in this case the input would be ambiguous.
org_per_seg
This feature makes relocatable/absolute mode local to the current segment.
Using
.ORG
when org_per_seg
is in
effect will only enable absolute mode for the current segment. Dito for
.RELOC
.
pc_assignment
Allow assignments to the PC symbol (`*' or `$' if dollar_is_pc
is enabled). Such an assignment is handled identical to the
.ORG
command (which is usually not needed, so just
removing the lines with the assignments may also be an option when porting
code written for older assemblers).
ubiquitous_idents
Allow the use of instructions names as names for macros and symbols. This makes it possible to "overload" instructions by defining a macro with the same name. This does also make it possible to introduce hard to find errors in your code, so be careful!
It is also possible to specify features on the command line using the
--feature
command line option.
This is useful when translating sources written for older assemblers, when
you don't want to change the source code.
As an example, to translate sources written for Andre Fachats xa65 assembler, the features
labels_without_colons, pc_assignment, loose_char_term
may be helpful. They do not make ca65 completely compatible, so you may not be able to translate the sources without changes, even when enabling these features. However, I have found several sources that translate without problems when enabling these features on the command line.
.FILEOPT, .FOPT
Insert an option string into the object file. There are two forms of this command, one specifies the option by a keyword, the second specifies it as a number. Since usage of the second one needs knowledge of the internal encoding, its use is not recommended and I will only describe the first form here.
The command is followed by one of the keywords
author
comment
compiler
a comma and a string. The option is written into the object file together with the string value. This is currently unidirectional and there is no way to actually use these options once they are in the object file.
 The command is followed by a
comma separated list of symbols to import. The command is similar to
.IMPORT
, but the import reference is always
written to the generated object file, even if the symbol is never referenced
(
.IMPORT
will not generate import
references for unused symbols).
Example:
.forceimport needthisone, needthistoo
See:
.IMPORT
.GLOBAL
Declare symbols as global. Must be followed by a comma separated list of
symbols to declare. Symbols from the list, that are defined somewhere in the
source, are exported, all others are imported. Additional
.IMPORT
or
.EXPORT
commands for the same symbol are allowed.
Example:
.global foo, bar
.GLOBALZP
Declare symbols as global. Must be followed by a comma separated list of
symbols to declare. Symbols from the list, that are defined somewhere in the
source, are exported, all others are imported. Additional
.IMPORTZP
or
.EXPORTZP
commands for the same symbol are allowed. The symbols
in the list are explicitly marked as zero page symbols.
Example:
.globalzp foo, bar
.HIBYTES
Define byte sized data by extracting only the high byte (that is, bits 8-15) from
each expression. This is equivalent to
.BYTE
with
the operator '>' prepended to each expression in its list.
Example:
.lobytes $1234, $2345, $3456, $4567
.hibytes $fedc, $edcb, $dcba, $cba9
which is equivalent to
.byte $34, $45, $56, $67
.byte $fe, $ed, $dc, $cb
Example:
.define MyTable TableItem0, TableItem1, TableItem2, TableItem3
TableLookupLo: .lobytes MyTable
TableLookupHi: .hibytes MyTable
which is equivalent to
TableLookupLo: .byte <TableItem0, <TableItem1, <TableItem2, <TableItem3
TableLookupHi: .byte >TableItem0, >TableItem1, >TableItem2, >TableItem3
See also:
.BYTE
,
.LOBYTES
,
.BANKBYTES
.I16
Valid only in 65816 mode. Switch the index registers to 16 bit.
Note: This command will not emit any code, it will tell the assembler to create 16 bit operands for immediate operands.
See also the
.I8
and
.SMART
commands.
.I8
Valid only in 65816 mode. Switch the index registers to 8 bit.
Note: This command will not emit any code, it will tell the assembler to create 8 bit operands for immediate operands.
See also the
.I16
and
.SMART
commands.
.IF
Conditional assembly: Evaluate an expression and switch assembler output on or off depending on the expression. The expression must be a constant expression, that is, all operands must be defined.
A expression value of zero evaluates to FALSE, any other value evaluates to TRUE.
.IFBLANK
Conditional assembly: Check if there are any remaining tokens in this line,
and evaluate to FALSE if this is the case, and to TRUE otherwise. If the
condition is not true, further lines are not assembled until an
.ESLE
,
.ELSEIF
or
.ENDIF
directive.
This command is often used to check if a macro parameter was given. Since an empty macro parameter will evaluate to nothing, the condition will evaluate to FALSE if an empty parameter was given.
Example:
.macro arg1, arg2
.ifblank arg2
lda #arg1
.else
lda #arg2
.endif
.endmacro
See also:
.BLANK
.IFCONST
Conditional assembly: Evaluate an expression and switch assembler output on or off depending on the constness of the expression.
A const expression evaluates to to TRUE, a non const expression (one containing an imported or currently undefined symbol) evaluates to FALSE.
See also:
.CONST
.IFDEF
Conditional assembly: Check if a symbol is defined. Must be followed by a symbol name. The condition is true if the the given symbol is already defined, and false otherwise.
See also:
.DEFINED
.IFNBLANK
Conditional assembly: Check if there are any remaining tokens in this line,
and evaluate to TRUE if this is the case, and to FALSE otherwise. If the
condition is not true, further lines are not assembled until an
.ELSE
,
.ELSEIF
or
.ENDIF
directive.
This command is often used to check if a macro parameter was given. Since an empty macro parameter will evaluate to nothing, the condition will evaluate to FALSE if an empty parameter was given.
Example:
.macro arg1, arg2
lda #arg1
.ifnblank arg2
lda #arg2
.endif
.endmacro
See also:
.BLANK
.IFNDEF
Conditional assembly: Check if a symbol is defined. Must be followed by a symbol name. The condition is true if the the given symbol is not defined, and false otherwise.
See also:
.DEFINED
.IFNREF
Conditional assembly: Check if a symbol is referenced. Must be followed by a symbol name. The condition is true if if the the given symbol was not referenced before, and false otherwise.
See also:
.REFERENCED
.IFP02
Conditional assembly: Check if the assembler is currently in 6502 mode
(see
.P02
command).
.IFP816
Conditional assembly: Check if the assembler is currently in 65816 mode
(see
.P816
command).
.IFPC02
Conditional assembly: Check if the assembler is currently in 65C02 mode
(see
.PC02
command).
.IFPSC02
Conditional assembly: Check if the assembler is currently in 65SC02 mode
(see
.PSC02
command).
.IFREF
Conditional assembly: Check if a symbol is referenced. Must be followed by a symbol name. The condition is true if if the the given symbol was referenced before, and false otherwise.
This command may be used to build subroutine libraries in include files (you may use separate object modules for this purpose too).
Example:
.ifref ToHex ; If someone used this subroutine
ToHex: tay ; Define subroutine
lda HexTab,y
rts
.endif
See also:
.REFERENCED
.IMPORT
Import a symbol from another module. The command is followed by a comma separated list of symbols to import, with each one optionally followed by an address specification.
Example:
.import foo
.import bar: zeropage
See:
.IMPORTZP
.IMPORTZP
Import a symbol from another module. The command is followed by a comma separated list of symbols to import. The symbols are explicitly imported as zero page symbols (that is, symbols with values in byte range).
Example:
.importzp foo, bar
See:
.IMPORT
.INCBIN
Include a file as binary data. The command expects a string argument that is the name of a file to include literally in the current segment. In addition to that, a start offset and a size value may be specified, separated by commas. If no size is specified, all of the file from the start offset to end-of-file is used. If no start position is specified either, zero is assumed (which means that the whole file is inserted).
Example:
; Include whole file
.incbin "sprites.dat"
; Include file starting at offset 256
.incbin "music.dat", $100
; Read 100 bytes starting at offset 200
.incbin "graphics.dat", 200, 100
.INCLUDE
Include another file. Include files may be nested up to a depth of 16.
Example:
.include "subs.inc"
.INTERRUPTOR
Export a symbol and mark it as an interruptor. This may be used together with the linker to build a table of interruptor subroutines that are called in an interrupt.
Note: The linker has a feature to build a table of marked routines, but it is your code that must call these routines, so just declaring a symbol as interruptor does nothing by itself.
An interruptor is always exported as an absolute (16 bit) symbol. You don't
need to use an additional .export
statement, this is implied by
.interruptor
. It may have an optional priority that is separated by a
comma. Higher numeric values mean a higher priority. If no priority is
given, the default priority of 7 is used. Be careful when assigning
priorities to your own module constructors so they won't interfere with the
ones in the cc65 library.
Example:
.interruptor IrqHandler
.interruptor Handler, 16
See the
.CONDES
command and the separate
section
Module constructors/destructors explaining
the feature in more detail.
.LINECONT
Switch on or off line continuations using the backslash character before a newline. The option is off by default. Note: Line continuations do not work in a comment. A backslash at the end of a comment is treated as part of the comment and does not trigger line continuation. The command must be followed by a '+' or '-' character to switch the option on or off respectively.
Example:
.linecont + ; Allow line continuations
lda \
#$20 ; This is legal now
.LIST
Enable output to the listing. The command must be followed by a boolean
switch ("on", "off", "+" or "-") and will enable or disable listing
output.
The option has no effect if the listing is not enabled by the command line
switch -l. If -l is used, an internal counter is set to 1. Lines are output
to the listing file, if the counter is greater than zero, and suppressed if
the counter is zero. Each use of .LIST
will increment or decrement the
counter.
Example:
.list on ; Enable listing output
.LISTBYTES
Set, how many bytes are shown in the listing for one source line. The default is 12, so the listing will show only the first 12 bytes for any source line that generates more than 12 bytes of code or data. The directive needs an argument, which is either "unlimited", or an integer constant in the range 4..255.
Examples:
.listbytes unlimited ; List all bytes
.listbytes 12 ; List the first 12 bytes
.incbin "data.bin" ; Include large binary file
.LOBYTES
Define byte sized data by extracting only the low byte (that is, bits 0-7) from
each expression. This is equivalent to
.BYTE
with
the operator '<' prepended to each expression in its list.
Example:
.lobytes $1234, $2345, $3456, $4567
.hibytes $fedc, $edcb, $dcba, $cba9
which is equivalent to
.byte $34, $45, $56, $67
.byte $fe, $ed, $dc, $cb
Example:
.define MyTable TableItem0, TableItem1, TableItem2, TableItem3
TableLookupLo: .lobytes MyTable
TableLookupHi: .hibytes MyTable
which is equivalent to
TableLookupLo: .byte <TableItem0, <TableItem1, <TableItem2, <TableItem3
TableLookupHi: .byte >TableItem0, >TableItem1, >TableItem2, >TableItem3
See also:
.BYTE
,
.HIBYTES
,
.BANKBYTES
.LOCAL
This command may only be used inside a macro definition. It declares a list of identifiers as local to the macro expansion.
A problem when using macros are labels: Since they don't change their name,
you get a "duplicate symbol" error if the macro is expanded the second time.
Labels declared with
.LOCAL
have their
name mapped to an internal unique name (___ABCD__
) with each macro
invocation.
Some other assemblers start a new lexical block inside a macro expansion.
This has some drawbacks however, since that will not allow any symbol
to be visible outside a macro, a feature that is sometimes useful. The
.LOCAL
command is in my eyes a better way
to address the problem.
You get an error when using
.LOCAL
outside
a macro.
.LOCALCHAR
Defines the character that start "cheap" local labels. You may use one of '@' and '?' as start character. The default is '@'.
Cheap local labels are labels that are visible only between two non
cheap labels. This way you can reuse identifiers like "loop
" without
using explicit lexical nesting.
Example:
.localchar '?'
Clear: lda #$00 ; Global label
?Loop: sta Mem,y ; Local label
dey
bne ?Loop ; Ok
rts
Sub: ... ; New global label
bne ?Loop ; ERROR: Unknown identifier!
.MACPACK
Insert a predefined macro package. The command is followed by an identifier specifying the macro package to insert. Available macro packages are:
atari Defines the scrcode macro.
cbm Defines the scrcode macro.
cpu Defines constants for the .CPU variable.
generic Defines generic macros like add and sub.
longbranch Defines conditional long jump macros.
Including a macro package twice, or including a macro package that redefines already existing macros will lead to an error.
Example:
.macpack longbranch ; Include macro package
cmp #$20 ; Set condition codes
jne Label ; Jump long on condition
Macro packages are explained in more detail in section Macro packages.
.MAC, .MACRO
Start a classic macro definition. The command is followed by an identifier (the macro name) and optionally by a comma separated list of identifiers that are macro parameters.
See section Macros.
.ORG
Start a section of absolute code. The command is followed by a constant
expression that gives the new PC counter location for which the code is
assembled. Use
.RELOC
to switch back to
relocatable code.
By default, absolute/relocatable mode is global (valid even when switching
segments). Using .FEATURE
org_per_seg
it can be made segment local.
Please note that you do not need .ORG
in most cases. Placing
code at a specific address is the job of the linker, not the assembler, so
there is usually no reason to assemble code to a specific address.
Example:
.org $7FF ; Emit code starting at $7FF
.OUT
Output a string to the console without producing an error. This command
is similar to .ERROR
, however, it does not force an assembler error
that prevents the creation of an object file.
Example:
.out "This code was written by the codebuster(tm)"
See also the
.WARNING
and
.ERROR
directives.
.P02
Enable the 6502 instruction set, disable 65SC02, 65C02 and 65816
instructions. This is the default if not overridden by the
--cpu
command line option.
.P816
Enable the 65816 instruction set. This is a superset of the 65SC02 and 6502 instruction sets.
.PAGELEN, .PAGELENGTH
Set the page length for the listing. Must be followed by an integer
constant. The value may be "unlimited", or in the range 32 to 127. The
statement has no effect if no listing is generated. The default value is -1
(unlimited) but may be overridden by the --pagelength
command line
option. Beware: Since ca65 is a one pass assembler, the listing is generated
after assembly is complete, you cannot use multiple line lengths with one
source. Instead, the value set with the last .PAGELENGTH
is used.
Examples:
.pagelength 66 ; Use 66 lines per listing page
.pagelength unlimited ; Unlimited page length
.PC02
Enable the 65C02 instructions set. This instruction set includes all 6502 and 65SC02 instructions.
.POPSEG
Pop the last pushed segment from the stack, and set it.
This command will switch back to the segment that was last pushed onto the
segment stack using the
.PUSHSEG
command, and remove this entry from the stack.
The assembler will print an error message if the segment stack is empty when this command is issued.
See:
.PUSHSEG
.PROC
Start a nested lexical level with the given name and adds a symbol with this
name to the enclosing scope. All new symbols from now on are in the local
lexical level and are accessible from outside only via
explicit scope specification. Symbols defined outside this local
level may be accessed as long as their names are not used for new symbols
inside the level. Symbols names in other lexical levels do not clash, so you
may use the same names for identifiers. The lexical level ends when the
.ENDPROC
command is read. Lexical levels
may be nested up to a depth of 16 (this is an artificial limit to protect
against errors in the source).
Note: Macro names are always in the global level and in a separate name space. There is no special reason for this, it's just that I've never had any need for local macro definitions.
Example:
.proc Clear ; Define Clear subroutine, start new level
lda #$00
L1: sta Mem,y ; L1 is local and does not cause a
; duplicate symbol error if used in other
; places
dey
bne L1 ; Reference local symbol
rts
.endproc ; Leave lexical level
.PSC02
Enable the 65SC02 instructions set. This instruction set includes all 6502 instructions.
.PUSHSEG
Push the currently active segment onto a stack. The entries on the stack include the name of the segment and the segment type. The stack has a size of 16 entries.
.PUSHSEG
allows together with
.POPSEG
to switch to another segment and to restore the old segment later, without
even knowing the name and type of the current segment.
The assembler will print an error message if the segment stack is already full, when this command is issued.
See:
.POPSEG
.RELOC
Switch back to relocatable mode. See the
.ORG
command.
.REPEAT
Repeat all commands between .REPEAT
and
.ENDREPEAT
constant number of times. The command is followed by
a constant expression that tells how many times the commands in the body
should get repeated. Optionally, a comma and an identifier may be specified.
If this identifier is found in the body of the repeat statement, it is
replaced by the current repeat count (starting with zero for the first time
the body is repeated).
.REPEAT
statements may be nested. If you use the same repeat count
identifier for a nested .REPEAT
statement, the one from the inner
level will be used, not the one from the outer level.
Example:
The following macro will emit a string that is "encrypted" in that all characters of the string are XORed by the value $55.
.macro Crypt Arg
.repeat .strlen(Arg), I
.byte .strat(Arg, I) ^ $55
.endrep
.endmacro
See:
.ENDREPEAT
.RES
Reserve storage. The command is followed by one or two constant expressions. The first one is mandatory and defines, how many bytes of storage should be defined. The second, optional expression must by a constant byte value that will be used as value of the data. If there is no fill value given, the linker will use the value defined in the linker configuration file (default: zero).
Example:
; Reserve 12 bytes of memory with value $AA
.res 12, $AA
.RODATA
Switch to the RODATA segment. The name of the RODATA segment is always "RODATA", so this is a shortcut for
.segment "RODATA"
The RODATA segment is a segment that is used by the compiler for readonly data like string constants.
See also the
.SEGMENT
command.
.SCOPE
Start a nested lexical level with the given name. All new symbols from now
on are in the local lexical level and are accessible from outside only via
explicit scope specification. Symbols defined
outside this local level may be accessed as long as their names are not used
for new symbols inside the level. Symbols names in other lexical levels do
not clash, so you may use the same names for identifiers. The lexical level
ends when the
.ENDSCOPE
command is
read. Lexical levels may be nested up to a depth of 16 (this is an
artificial limit to protect against errors in the source).
Note: Macro names are always in the global level and in a separate name space. There is no special reason for this, it's just that I've never had any need for local macro definitions.
Example:
.scope Error ; Start new scope named Error
None = 0 ; No error
File = 1 ; File error
Parse = 2 ; Parse error
.endscope ; Close lexical level
...
lda #Error::File ; Use symbol from scope Error
.SEGMENT
Switch to another segment. Code and data is always emitted into a segment, that is, a named section of data. The default segment is "CODE". There may be up to 254 different segments per object file (and up to 65534 per executable). There are shortcut commands for the most common segments ("CODE", "DATA" and "BSS").
The command is followed by a string containing the segment name (there are
some constraints for the name - as a rule of thumb use only those segment
names that would also be valid identifiers). There may also be an optional
address size separated by a colon. See the section covering
address sizes
for more information.
The default address size for a segment depends on the memory model specified on the command line. The default is "absolute", which means that you don't have to use an address size modifier in most cases.
"absolute" means that the is a segment with 16 bit (absolute) addressing. That is, the segment will reside somewhere in core memory outside the zero page. "zeropage" (8 bit) means that the segment will be placed in the zero page and direct (short) addressing is possible for data in this segment.
Beware: Only labels in a segment with the zeropage attribute are marked as reachable by short addressing. The `*' (PC counter) operator will work as in other segments and will create absolute variable values.
Please note that a segment cannot have two different address sizes. A segment specified as zeropage cannot be declared as being absolute later.
Examples:
.segment "ROM2" ; Switch to ROM2 segment
.segment "ZP2": zeropage ; New direct segment
.segment "ZP2" ; Ok, will use last attribute
.segment "ZP2": absolute ; Error, redecl mismatch
See:
.BSS
,
.CODE
,
.DATA
and
.RODATA
.SETCPU
Switch the CPU instruction set. The command is followed by a string that
specifies the CPU. Possible values are those that can also be supplied to
the
--cpu
command line option,
namely: 6502, 6502X, 65SC02, 65C02, 65816, sunplus and HuC6280. Please
note that support for the sunplus CPU is not available in the freeware
version, because the instruction set of the sunplus CPU is "proprietary
and confidential".
See:
.CPU
,
.IFP02
,
.IFP816
,
.IFPC02
,
.IFPSC02
,
.P02
,
.P816
,
.PC02
,
.PSC02
.SMART
Switch on or off smart mode. The command must be followed by a '+' or '-' character to switch the option on or off respectively. The default is off (that is, the assembler doesn't try to be smart), but this default may be changed by the -s switch on the command line.
In smart mode the assembler will do the following:
REP
and SEP
instructions in 65816 mode
and update the operand sizes accordingly. If the operand of such an
instruction cannot be evaluated by the assembler (for example, because
the operand is an imported symbol), a warning is issued. Beware: Since
the assembler cannot trace the execution flow this may lead to false
results in some cases. If in doubt, use the .Inn
and .Ann
instructions to tell the assembler about the current settings.RTS
instruction by RTL
if it is
used within a procedure declared as far
, or if the procedure has
no explicit address specification, but it is far
because of the
memory model used.Example:
.smart ; Be smart
.smart - ; Stop being smart
.STRUCT
Starts a struct definition. Structs are covered in a separate section named "Structs and unions".
See:
.ENDSTRUCT
.SUNPLUS
Enable the SunPlus instructions set. This command will not work in the freeware version of the assembler, because the instruction set is "proprietary and confidential".
See:
.P02
,
.PSC02
,
.PC02
, and
.P816
.TAG
Allocate space for a struct or union.
Example:
.struct Point
xcoord .word
ycoord .word
.endstruct
.bss
.tag Point ; Allocate 4 bytes
.WARNING
Force an assembly warning. The assembler will output a warning message
preceded by "User warning". This warning will always be output, even if
other warnings are disabled with the
-W0
command line option.
This command may be used to output possible problems when assembling the source file.
Example:
.macro jne target
.local L1
.ifndef target
.warning "Forward jump in jne, cannot optimize!"
beq L1
jmp target
L1:
.else
...
.endif
.endmacro
See also the
.ERROR
and
.OUT
directives.
.WORD
Define word sized data. Must be followed by a sequence of (word ranged, but not necessarily constant) expressions.
Example:
.word $0D00, $AF13, _Clear
.ZEROPAGE
Switch to the ZEROPAGE segment and mark it as direct (zeropage) segment. The name of the ZEROPAGE segment is always "ZEROPAGE", so this is a shortcut for
.segment "ZEROPAGE", zeropage
Because of the "zeropage" attribute, labels declared in this segment are addressed using direct addressing mode if possible. You must instruct the linker to place this segment somewhere in the address range 0..$FF otherwise you will get errors.
See:
.SEGMENT


--- title: HOW IT WORKS pagina: How it works group: "navigation" order: 2 --- {% include head.html %}
{% include nav.html %}Funding a Request will only take you a minute. You can issue a reward for any bug you want to see fixed or feature you want to see implemented. Thanks to Ethereum's Smart Contracts, the reward goes straight to the developers resolving the issue –no need for a middle man.
Funding any goal or issue will be painless and easy, thanks to an intuitive front-end application for online and mobile use. One of the milestones we've included in our roadmap is the development of a Chrome browser add-on so that you can fund issues on your favorite platform.
Still want to find out more?
Dig into our Documentation Center or check out our early alpha release.
Anyone can fund requests for their favorite open source projects, accelerating their development.
Reward developers for their contributions to open-source projects.
Developers can find out what issues are most important to the community.
By proposing or funding new features, you actively participate in the development of the software.


Before Change
spike = 1
output_b_l_t[b, l, t] = spike
return np.cumsum(np.asarray(output_b_l_t, bool), 2)
def reset(self, sample_idx):
After Change
and sim_step % 1 == 0:
if self.config.getboolean("conversion", "use_isi_code"):
first_spiketimes_b_l = np.argmax(output_b_l_t, 2)
undecided_b = np.sum(first_spiketimes_b_l, 1) == 0
first_spiketimes_b_l[np.nonzero(np.sum(
output_b_l_t, 2) == 0)] = self._num_timesteps
guesses_b = np.argmin(first_spiketimes_b_l, 1)
else:
spike_sums_b_l = np.sum(output_b_l_t, 2)
undecided_b = np.sum(spike_sums_b_l, 1) == 0
guesses_b = np.argmax(spike_sums_b_l, 1)
none_class_b = -1 * np.ones(self.batch_size)
clean_guesses_b = np.where(undecided_b, none_class_b, guesses_b)
echo("{:.2%}_".format(np.mean(kwargs[str("truth_b")] ==
clean_guesses_b)))
if self.config.getboolean("conversion", "use_isi_code") and \


Graphs
Dashboard
Graphs
Operating System
Operating System and Version
Access Status
Operating System
No Information is available


Generate Room
Nickname:
Join Room
Deck
Card Title:
Category
Album
Book
Cartoon/Anime
Character
Comic Book/Manga
Fine Art
Game
Movie
Musical/Play
Person
Song
TV Show
Category
Album
Book
Cartoon/Anime
Character
Comic Book/Manga
Fine Art
Game
Movie
Musical/Play
Person
Song
TV Show
Category
Album
Book
Cartoon/Anime
Character
Comic Book/Manga
Fine Art
Game
Movie
Musical/Play
Person
Song
TV Show
Category
Album
Book
Cartoon/Anime
Character
Comic Book/Manga
Fine Art
Game
Movie
Musical/Play
Person
Song
TV Show
Category
Album
Book
Cartoon/Anime
Character
Comic Book/Manga
Fine Art
Game
Movie
Musical/Play
Person
Song
TV Show
Category
Album
Book
Cartoon/Anime
Character
Comic Book/Manga
Fine Art
Game
Movie
Musical/Play
Person
Song
TV Show
Category
Album
Book
Cartoon/Anime
Character
Comic Book/Manga
Fine Art
Game
Movie
Musical/Play
Person
Song
TV Show
Submit Deck
Player
Ready
Start Game
Viewed Cards
Correct Guesses
Submit
Card name will show up here
00:00
Comic Book/Manga
Click for next card
Score T1
Score T2
Team 1
Team 2
Ready
Start Round
Start Turn
Team 1 Cards
Team 2 Cards


Game of Produce:
Song of The Sweet Potato
The sweet potato is one of the world's most delicious vegetables. It's so loaded with beta carotene and vitamins that if you ate one sweet potato every day, you would develop super powers. No, really.
Other fun facts about sweet potatoes
- They are roots, not tubers.
- They can be juiced. (We don't recommend it though.)
- George Washington grew sweet potatoes on his farm back in the day.
Cool people who endorse sweet potatoes
- The Dalai Lama
- Barack Obama
- Ada Lovelace


Welcome to GS1 Resolver's Data Entry Service
Upload data to GS1 Resolver
Download your data from GS1 Resolver
Link Types accepted by this GS1 Resolver


Lab Visitors
Frenk van Harreveld
Frenk van Harreveld is an associate professor of social psychology at the University of Amsterdam. Subsequent to obtaining his PhD at the University of Amsterdam he worked for the world’s largest consulting firm Accenture, after which he returned to academia. He has worked as a visiting researcher at the University of California, Berkeley and the University of Massachusetts, Amherst and the University of British Columbia in Vancouver. His research concerns various aspects of uncertainty. Frenk’s research on attitudes and decision-making examines various forms of evaluative conflict such as attitudinal ambivalence, decision reversibility and regret. Other forms of uncertainty that he investigates are risk perception, lack of control and mortality salience. Frenk is Head of Studies at the Politics, Psychology, Law and Economics (PPLE) bachelor program of the University of Amsterdam and Strategic Research Program coordinator at the National Institute for Public Health and Safety.
Matthew D. Rocklage
I’m a South Dakota native who earned my PhD in social psychology with a minor in statistics and quantitative methods at Ohio State University working with Dr. Russ Fazio. I’m currently a postdoctoral researcher of marketing at Northwestern University in the Kellogg School of Management.
方雪 Xue Fang
化学 2015级本科 (Chemistry 2015)
Xue is a fourth year student of school of physical science and technology in ShanghaiTech, major in chemistry, minor in innovation and entrepreneurship. Taking taekwondo, painting, piano and traveling as hobbies, Xue has a comprehensive background. Willing to challenge new field, also good at observing and analyzing details, she prefers to be an instructor in the future. Presently, she is working on educational psychology, habit formation and the recovery of failure, trying to develop a more effective education mode through research so as to help those who have trouble persisting on a task realize their goals.
曾理 Li Zeng
计算机 2017级本科 (CS 2017)
就读于上海科技大学信息科学与技术学院计算机科学与技术专业。热爱运动，擅长分析和计算。 理想是成为一名计算机科学领域研究人员。对社会心理学和人工智能有一定的兴趣，希望能在ARLab对相关课题做一定的研究，并积累自己的研究经验，锻炼研究能力。
翁光源 Guangyuan (Gideon) Weng
计算机 2017级本科 (CS 2017)
I’m an undergraduate student who is eager to comprehend the world. In addition to website and app development, I have a certain understanding of the visual art creation based on Processing. The application of machine learning in user behavior prediction and user value assessment also attracts me to a great extent.


This application uses “ES Modules”, which apparently are not supported or enabled in your browser.
By Dave BriccettiSource code


The purpose of this test is to measure the memory read latencies.
You can notice 3 different latencies levels. The first small one is related to L1 cache. The second latency is related to L2 cache and the third much larger latency is the DDR memory latency.
The first column is is the size of a block of memory repeatedly read in. The second column is the latency in ns. A small block will be cached, so you see fast latency. A larger block will not fit into cache.


Neural Novels
Baseline
. Two layer GRU char rnn trained for 60 epochs on 4000000 characters of Project Gutenberg G.A. Henty novels. I got the books from a dataset of 3036 cleaned project gutenberg novels that I found
here


Even after all the translations are complete, there may be a need to replace a certain executable with a newer version containing a bug fix or a feature enhancement. You will be able to do this quickly and effectively by using the Update feature in the File menu.
To make this feature work, you must first put the updated geode and .vm file in the proper source directory, overwriting the original files. Then, by clicking Update Translation File (in the Update submenu of the File menu), the existing Translation File will be compared with the new strings in the geode, showing the new or changed chunks, as well as the ones left unchanged. The deleted chunks will be grouped in a separate resource named "Deleted chunks" at the end of the resource list. You will then be able to make the necessary modifications to this file to bring it up to date with the newest version of the geode.
If the name of the original-language geode has changed, you will need to use the Update Geode Name function (in the Update submenu of the File menu) to tell ResEdit about the new name.
After updating the Translation File, you can then create an updated local-language executable as out lined above.
If there have been no changes to the geode that affect editable chunks (as when code changes for a bug fix), it is also possible to simply rebuild the new geode from the existing Translation File by choosing Create A New Executable from the File menu.
After viewing the updated Translation File and making any necessary changes, you can remove the updating information from the Translation File by choosing Commit the Update trigger from the File/Update menu. This will remove information which marks the chunks as "new" or "changed" as well as remove the Deleted Chunks resource.