Seven-day week. The seven-day week is used by the majority of the world and is the international standard as specified in ISO 8601. Origins[edit] The origin of the seven-day week is the religious significance that was placed on the seventh day by ancient cultures, including the Babylonian and Jewish civilizations. Babylonians celebrated a holy day every seven days, starting from the new moon, then the first visible crescent of the Moon, but adjusted the number of days of the final "week" in each month so that months would continue to commence on the new moon. (The seven-day week is only 23.7% of a lunation, so a continuous cycle of seven-day weeks rapidly loses synchronization with the lunation.)
Jews celebrated every seventh day, within a continuous cycle of seven-day weeks, as a holy day of rest from their work, in remembrance of Creation week. Ancient Near East[edit] Classical Antiquity[edit] Christian Europe[edit] Other systems[edit] China[edit] Japan[edit] Hindu[edit] France[edit] Soviet Union[edit] Sunday. Various Calendar Programs. This directory contains some PostScript programs that may generate nice looking (at least to my eyes) printed calendars when sent to a PostScript printer. Not elaborate calendars with local and/or variable holidays like Easter (you may want to check emacs for this) but still very usable. Two group of calendar utilities are considered: the first one will print a single month calendar on a paper sheet (month-family); the second one (year-family) will print a whole year calendar on a paper sheet. At the end, we will make some considerations about calculations connected to calendars, with the corresponding C++ code.
Summary of what's here Month calendars All these programs are based on the same original code (public domain), that I retrieved from (I think) comp.sources.postscript; it was labeled: % PostScript program to draw calendar % Copyright (C) 1987 by Pipeline Associates, Inc. % Permission is granted to modify and distribute this free of charge. That original code had some problems: ISO week date. The ISO week date system is a leap week calendar system that is part of the ISO 8601 date and time standard. The system is used (mainly) in government and business for fiscal years, as well as in timekeeping. The system specifies a week year atop the Gregorian calendar by defining a notation for ordinal weeks of the year.
The Gregorian leap cycle, which has 97 leap days spread across 400 years, contains a whole number of weeks (20871). In every cycle there are 71 years with an additional 53rd week. An average year is exactly 52.1775 weeks long, months average at 4.348125 weeks. An ISO week-numbering year (also called ISO year informally) has 52 or 53 full weeks. That is 364 or 371 days instead of the usual 365 or 366 days. A date is specified by the ISO week-numbering year in the format , a week number in the format prefixed by the letter 'W', and the weekday number, a digit from 1 through 7, beginning with Monday and ending with Sunday. Relation with the Gregorian calendar[edit] Online calculator: Week number of a given date. Guide — C/C++ Development with Eclipse. Zum Hinzufügen von Unterstützung für VBScript MFC-Anwendung hosing. Sie können VBA-ähnliche scripting-Funktion Ihre MFC hinzufügen mit wenig Aufwand, die Microsoft ActiveX Scripting-Technologien verwendet die Anwendung.
Dieser Artikel beschreibt eine neue MFC-Anwendung erstellen oder ändern ein vorhandenes, die Unterstützung für VBScript integriert. dim x dim y dim z x = 101*199 y = 313*199 z = gcd(x, y) ShowValue "gcd(" & x & ", " & y & ") = ", z HelpAbout Grundlegende Arbeitsablauf lautet wie folgt: Starten Sie das VBScript Modul vbscript.dll, und Schnittstellen IActiveScript und IActiveScriptParse zu erhalten.Sie geben dem VBScript-Modul die Implementierung von IActiveScriptSite, die das Modul später, verwendet um abrufen und aufrufen, um Ihre Objekte.Sie fügen die Objekte, die Sie implementieren und zu Skripts zur Verfügung stellen durch IActiveScript::AddNamedItem() aufrufen möchten.Sie bereitstellen, den Skripttext, der über IActiveScriptParse::ParseScriptText() ausführen. . ( ) Maschinell übersetzter Artikel. AXS_FAQ - Hosting - Debugger. Hosting – Debugger How can I launch the debugger and have it stop on a breakpoint in my script similar to what Internet Explorer does?
You'll need to make your app a "smart host". Essentially, that means you go through a series of steps to launch the debugger when appropriate, set breakpoints to cause the debugger to stop, etc. You can still rely on an external debugger (like Visual Interdev, etc) for debugging itself. (Source: mark_baker@mindspring.com , Mark Baker, 2/11/2000, microsoft.public.scripting.hosting ) Back to Table of Contents I want to implement support for Active Script Debugging.
Get the file "scriptng.exe" from the Microsoft site. (Source: mark_baker@mindspring.com, Mark Baker, 10/20/99, microsoft.public.scripting.hosting ) You can get the files you need from: Q223389 - FILE: Scriptng.EXE Has Files To Add Active Debugging Back to Table of Contents Here are the steps to do this: Back to Table of Contents. Adding Debug facilities to an Active Scripting Host.
Introduction This article follows on from the Active Script Hosting discussions of Andrew Garbuzov. Before you start on adding debugger support to your active script it's probably a good idea to have active scripts up and running.... The code in this article builds on the Microsoft sample : " MFCAXS.EXE: MFCAXS Implements an Active Script Host Using MFC ". This sample on its own is really a very good place to discover lots about how to implement Active Script Hosting.
To experiment with the debugging interfaces, you will need an Active Script debugger installed like the IE4 one available from Microsoft's scripting site A reference for the Active Script debugging interfaces was once provided in the online reference but this now seems to have been moved off the Microsoft site. Debugging in Action Before you start please Download demo project and extract and run mfcaxscrb.exe and also have the Microsoft Active Script Engines and the IE4 debugger installed.
To view the debugger in action: ?? 1. Windows Script Interfaces. Windows Script interfaces fall into two categories: Windows Script hosts and Windows Script engines. A host creates a scripting engine and calls on the engine to run the scripts. Examples of Windows Script hosts include: Microsoft Internet Explorer Internet authoring tools Shell Windows Script engines can be developed for any language or run-time environment, including: Microsoft Visual Basic Scripting Edition (VBScript) Perl Lisp To make implementation of the host as flexible as possible, an OLE Automation wrapper for Windows Script is provided.
The Windows Script design isolates the interface elements required only in an authoring environment so that nonauthoring hosts (such as browsers and viewers) and script engines (for example, VBScript) can be kept lightweight. The following illustration shows the interaction between a Windows Script host and an Windows Script engine. The steps involved in the interaction between the host and engine are given in the following list. Active Scripting APIs: Add Powerful Custom Debugging to Your Script-Hosting App. Any developers today use scripting in their applications to add software functionality such as macro language facilities and other user-customizable features. Microsoft has fueled this trend in recent years with their release of the Active Scripting COM interfaces.
One of the questions that arises when scripting support is integrated into a product is how to debug it. For certain apps, the use of Microsoft's free script debugger (available at is a good choice. However, you may have applications that need an integrated debugging solution. Active Debugging Framework When Microsoft designed the Active Scripting framework, they were very careful about partitioning the debugging functionality of the system. Figure 1 Active Scripting Debugger Framework In the next five sections, I'll briefly explore each component, then use them to create a real application debugger.
Application Debugger Language Engine Process Debug Manager Machine Debug Manager Host Interfaces. So schreibt man Debugger für das Active Scripting. Veröffentlicht: 15. Dez 2001 | Aktualisiert: 09. Nov 2004 Von Mike Pellegrino Die Active Scripting-Schnittstellen erlauben es nicht nur, beliebige Anwendungen mit beliebigen Skriptsprachen auszustatten, sondern auch noch, eigene Debugger dafür zu schreiben. Auf dieser Seite Diesen Artikel können Sie hier lesen dank freundlicher Unterstützung der Zeitschrift: Heutzutage setzen viele Entwickler in Ihren Anwendungen Skriptsprachen ein, um die Funktionalität zu erweitern, zum Beispiel in Form von Makro-Sprachen. Wenn ein Produkt nun eine Skriptsprache anbietet, stellt sich sofort die Frage, wie man eigentlich die Fehler im Skript findet.
Diesen Anforderungen war man sich bei Microsoft schon beim Entwurf des Active Scripting Frameworks bewusst und hat entsprechende Möglichkeiten vorgesehen, die es den Anwendungen von Drittanbietern erlaubt, den Skriptcode im eigenen Adressraum zu debuggen. Das Active Debugging Framework B1 Der Debugger im Active Scripting Framework. (??? Anwendungsdebugger.