text:
Radiation Oncology/Toxicity/Rectum

Rectum Toxicity
 * Also please see Toxicity/Pelvis

Scoring

 * Christie Hospital; 2002 PMID 12443807 -- "Scoring of treatment-related late effects in prostate cancer." (Livsey JE, Radiother Oncol. 2002 Nov;65(2):109-21.)
 * Comparison of LENT/SOMA, UCLA Prostate Cancer Index, and RAND Health survey (SF-36)
 * Conclusion: LENT/SOMA more wide-ranging and more informative than UCLA

 * Vienna; 2000 PMID 10719695 -- "Endoscopic scoring of late rectal mucosal damage after conformal radiotherapy for prostatic carcinoma." (Wachter S, Radiother Oncol. 2000 Jan;54(1):11-9.)
 * Prospective. 44 patients, treated with 3D-CRT 66/33 for prostate CA. Flexible rectosigmoidoscopy. Developed 6-scale score

2D RT vs 3D-CRT

 * Rotterdam, Netherlands (1994-1996) -- conformal RT vs conventional RT
 * Randomized. 266 patients, prostate cancer Stage T1-4N0. RT 66/33. Arm 1) conventional RT (rectangular, open fields) vs. Arm 2) conformal RT (conformally shaped fields with MLC). PTV = GTV + 1.5 cm
 * 1999 PMID 10098427 -- "Acute morbidity reduction using 3DCRT for prostate carcinoma: a randomized study." (Koper PC, Int J Radiat Oncol Biol Phys. 1999 Mar 1;43(4):727-34.)
 * Outcome: Acute GI Grade 2 conventional 32% vs. conformal 19% (SS); Acute GU Grade 2 in 17% vs. 18% (NS). Further GI analysis: rectal symptoms 18% vs. 14% (NS) but anal symptoms 16% vs. 8% (SS)
 * Conclusion: Significant reduction in GI toxicity, driven by anal symptoms. No difference between rectum/sigmoid and bladder toxicity

 * Royal Marsden (1988-1995) -- conformal RT vs conventional RT
 * Randomized, extension of original pelvic randomized trial. 225 men with prostate CA, T1-T4N0. NACHT in 68%. RT 64/32. Arm 1) conformal RT vs. Arm 2) conventional RT
 * 1999 PMID 9929018 -- "Comparison of radiation side-effects of conformal and conventional radiotherapy in prostate cancer: a randomised trial." (Dearnaley DP, Lancet. 1999 Jan 23;353(9149):267-72.) Median F/U 3.6 years
 * Outcome: Radiation-induced proctitis G1+ conformal RT 37% vs. conventional RT 56% (SS), G2+ 5% vs. 15% (SS). No difference in bladder toxicity. No difference in bPFS (78% vs 83%, NS)
 * Conclusion: Conformal RT significantly reduced risk of later proctitis
 * 1997 (1988-1993) PMID 9106921 -- "Acute toxicity in pelvic radiotherapy; a randomised trial of conformal versus conventional treatment." (Tait DM, Radiother Oncol. 1997 Feb;42(2):121-36.)
 * Initial randomized study of pelvic RT. 266 patients (prostate 52%, bladder 41%, rectum/other 7%). Most common dose 64/32, but some bladder CA patients 30-36/5-6 fractions
 * Outcome: No statistically significant difference between acute symptoms or medications prescribed
 * Conclusion: Late effects must be collected/analyzed

3D-CRT vs IMRT

 * Dutch CKVO96-10 PMID 18718725 -- "Role of intensity-modulated radiotherapy in reducing toxicity in dose escalation for localized prostate cancer." (Al-Mamgani A, Int J Radiat Oncol Biol Phys. 2009 Mar 1;73(3):685-91. Epub 2008 Aug 19.)
 * Unplanned subset analysis. Dutch randomized dose-escalation trial, subset treated at same institution to 78 Gy using 2 techniques: 3D-CRT sequential boost 78/39 (68/34 + 10/5) or IMRT simultaneous integrated boost 78/39 (PTV1 68/39 and PTV2 78/39). Median F/U 3DCRT 6.3 years, IMRT 4.7 years
 * Outcome: 5-year bPFS IMRT 70% vs 3DCRT 61% (NS)
 * Acute toxicity: GI G2+ IMRT 20% vs. 3DCRT 61% (SS); GI G3+ 0% vs 13% (SS); acute GU toxicity 53% vs. 69% (NS)
 * Late toxicity: GI G2+ IMRT 21% vs. 3DCRT 37% (NS); GI G3+ 0% vs 7% (NS); late GU toxicity 43% vs. 45% (NS)
 * Conclusion: IMRT reduced toxicity without compromising outcomes

 * Memorial Sloan Kettering; 2001 (1988-1998) PMID 11490237 -- "High dose radiation delivered by intensity modulated conformal radiotherapy improves the outcome of localized prostate cancer." (Zelefsky MJ, J Urol. 2001 Sep;166(3):876-81.)
 * Retrospective. 1100 patients with cT1c-T3N0, treated with 3D-CRT or IMRT.
 * Outcome: 5-year bPFS favorable risk 85%, intermediate risk 58%, unfavorable risk 38% (SS)
 * Late rectal toxicity (81 Gy group): 3D-CRT 14% vs IMRT 2% (SS); no impact of IMRT on GU toxicity
 * Conclusion: IMRT associated with minimal rectal toxicity, represents most favorable risk-to-benefit ratio

DVH Models

 * QUANTEC; 2010 PMID 20171506 -- "Radiation dose-volume effects in radiation-induced rectal injury." (Michalski JM, Int J Radiat Oncol Biol Phys. 2010 Mar 1;76(3 Suppl):S123-9.)
 * Rectum segmentation recommendation: Above anal verge to turn into sigmoid
 * Models: LKB parameters n=0.09, m=0.13, TD50=76.9
 * DVH constraint recommendations: V50 <50%, V60 <35%, V65 <25%, V70 <20%, V75 <15%. Hypofractionated schedules should be adjusted using conservative rectum a/b = 3

 * MRC RT01; 2010 PMID 19540054 -- "Dose-volume constraints to reduce rectal side effects from prostate radiotherapy: evidence from MRC RT01 Trial ISRCTN 47772397." (Gulliford SL, Int J Radiat Oncol Biol Phys. 2010 Mar 1;76(3):747-54. Epub 2009 Jun 18.)
 * Retrospective. DVH analysis from randomized dose-escalation trial. 7 clinically relevant rectal toxicity endpoints
 * Outcome: DVH constraints: V30 <= 80%, V40 <= 65%, V50 <= 55%, V60 <= 40%, V65 <= 30%, V70 <= 15%, and V75 <= 3%
 * Conclusion: Entire DVH distribution should be considered to reduce rectal toxicity

 * Tubingen, Germany; 2007 PMID 17707277 -- "Principal component analysis-based pattern analysis of dose-volume histograms and influence on rectal toxicity." (Sohn M, Int J Radiat Oncol Biol Phys. 2007 Sep 1;69(1):230-9.)
 * Principal component analysis. 262 patients, 4-F 3D-CRT. Correlation of first 3 PCs (96% of DVH shape variability) to Grade 2+ rectal bleeding
 * Outcome: PC1 correlated with mean dose, PC2 volume in field overlap, PC3 maximal dose. Only PC2 correlated with toxicity
 * Conclusion: CPA can provide information about DVH shape and its relationship to toxicity

 * Princess Margaret; 2007 (1997-2003) PMID 17379434 -- "Patient-assessed late toxicity rates and principal component analysis after image-guided radiation therapy for prostate cancer." (Skala M, Int J Radiat Oncol Biol Phys. 2007 Jul 1;68(3):690-8. Epub 2007 Mar 26.)
 * Retrospective. 690 men treated for PCA with RT 75.6-79.8 Gy using 3D-CRT of IMRT. Questionnaires sent, received from 63%. Median F/U 2 years
 * Late toxicity: GI G1 25%, G2 2.5%, G3 0.7%; GU 16%, 9%, 0.9%. Erectile function sufficient for intercourse in 68%
 * Dosimetric models: No dosimetric parameter, including principal component analysis, correlated with late toxicity
 * Conclusion: Incidence of toxicity low, with lack of correlation to dosimetric parameters

 * William Beaumont, 2007 PMID 17258870 -- "Incidence of late rectal bleeding in high-dose conformal radiotherapy of prostate cancer using equivalent uniform dose-based and dose-volume-based normal tissue complication probability models." (Sohn M, Int J Radiat Oncol Biol Phys. 2007 Jan 25; [Epub ahead of print])
 * Retrospective. 319 patients. Models using EUD and DVH NTCP to predict chronic Grade 2+ rectal bleeding. Median F/U 2.8 years (0.1-6.4)
 * Toxicity: Grade 2+ bleeding in 16%
 * Lyman model: TD50 = 78.4 Gy, n=0.08, m=0.108
 * Conclusion: clear confirmation of volume effect, and no correlation with mean dose

 * MD Anderson
 * 2006 PMID 16504763 -- "Cluster model analysis of late rectal bleeding after IMRT of prostate cancer: a case-control study." (Tucker SL, Int J Radiat Oncol Biol Phys. 2006 Mar 15;64(4):1255-64.)
 * Paired case-control study, 9 patients with Grade 2+ late rectal toxicity compared with similar DVH patients without toxicity.
 * Outcome: Patients with rectal toxicity had significantly larger mean maximum damaged cluster size. Highest prediction of difference at doses ~30 Gy
 * Conclusion: Cluster model incorporates spatial information beyond DVH
 * 2004 PMID 15590191 -- "Comparison of rectal dose-wall histogram versus dose-volume histogram for modeling the incidence of late rectal bleeding after radiotherapy." (Tucker SL, Int J Radiat Oncol Biol Phys. 2004 Dec 1;60(5):1589-601.)
 * Planning comparison. Dose-volume histograms (DVH) vs dose-wall histograms (DWH) in 128 patients treated with 3D-CRT. Fit to 4 models (Lyman, mean-dose, parallel-architecture, cutoff-dose). Minimum 2 year F/U
 * Slightly better performance for DWH model. Intermediate dose cut-off predicted as V32 >80%
 * Conclusion: NTCP models fit slightly better with DWH as opposed to DVH
 * 2004 (1992-1999) PMID 15050331 -- "Characterization of rectal normal tissue complication probability after high-dose external beam radiotherapy for prostate cancer." (Cheung R, Int J Radiat Oncol Biol Phys. 2004 Apr 1;58(5):1513-9.)
 * Retrospective. 128 patients treated with 3D-CRT to 78 Gy. Endpoint Grade 2+ rectal bleeding. Minimal F/U 2 years
 * Toxicity: Grade 2+ bleeding 23%
 * Lyman model: TD50 = 53.6 Gy, n = 3.91, m = 0.156. Different with/without hemorrhoids
 * Conclusion: Possibly large volume effect; LKB model should be used with caution
 * 2002 (1993-1998) PMID 12128107 -- "Prostate cancer radiation dose response: results of the M. D. Anderson phase III randomized trial." (Pollack A, Int J Radiat Oncol Biol Phys. 2002 Aug 1;53(5):1097-105.). Median F/U 5 years
 * Dosimetric analysis of randomized trial. 301 T1-T3 patients, stratified by PSA <10 (65%), 10-20 (35%), >20 (few). Arm 1) 70 Gy vs. Arm 2) 78 Gy. Technique 4F 46/23, Arm 1) 4F RF 24/12, Arm 2) 3D-CRT 6 fields 32/16. CTV = prostate/SV, margin 1.5 cm anterior/inferior, 1.0 cm posterior/superior. No hormones
 * Toxicity: Grade 2+ rectal toxicity 12% vs. 26% (p=0.001); Grade 2+ bladder toxicity NS. Less GI toxicity, if V70 <25% (16% G2) vs if V70 >25% (46% G2)
 * Conclusion: Highly significant FFF improvement for intermediate-to-high risk patients, no benefit if PSA <10. Increased rectal toxicity

 * Netherlands Cancer Institute; 1998 PMID 9588921 -- "Estimation of the incidence of late bladder and rectum complications after high-dose (70-78 GY) conformal radiotherapy for prostate cancer, using dose-volume histograms." (Boersma LJ, Int J Radiat Oncol Biol Phys. 1998 Apr 1;41(1):83-92.)
 * Retrospective. 130 patients, localized prostate cancer on dose escalating protocol 70 -> 78 Gy. Median F/U 2 years
 * Outcome: Severe rectal bleeding if rectal wall V65> 40%, V70 >30%, or V75 >5%
 * Conclusion: Dose escalation is feasible, but incidence of severe late rectal bleeding is increased above certain DVH constraints

Gene Profiling

 * Milan, Italy; 2009 PMID 19211196 -- "To bleed or not to bleed. A prediction based on individual gene profiling combined with dose-volume histogram shapes in prostate cancer patients undergoing three-dimensional conformal radiation therapy." (Valdagni R, Int J Radiat Oncol Biol Phys. 2009 Aug 1;74(5):1431-40. Epub 2009 Feb 11.)
 * Retrospective. 30 patients, 3D-CRT to >70 Gy. Low-risk bleeding group (V70 <20% and V50 <55%) and bleeding; high-risk group (V70 >25% and V50 >60%) and bleeding, and high-risk group and no bleeding. PCR on lymphoblastoid RNA from peripheral mononucleated cells
 * Outcome: nine genes downregulated in low-risk bleeder group; four genes upregulated in high-risk non-bleeder group
 * Conclusion: Predictive value of gene panels promising

Rectal Balloons

 * Nijmegen, The Netherlands (2002) -- 3D-CRT +/- endorectal balloon
 * Randomized. 48 patients, treated with 3D-CRT to 67.5/30. Arm 1) No endorectal balloon (ERB-) vs. Arm 2) with endorectal balloon (ERB+). PTV = prostate + SV + 9 mm margin. Rectosigmoidoscopy at 3 months, 6 months, 1 year, 2 years. 146 endoscopies and 2,336 mucosal areas analyzed
 * 2007 PMID 17161552 -- "Reduced late rectal mucosal changes after prostate three-dimensional conformal radiotherapy with endorectal balloon as observed in repeated endoscopy." (van Lin EN, Int J Radiat Oncol Biol Phys. 2007 Mar 1;67(3):799-811. Epub 2006 Dec 8.) Median F/U 2.5 years
 * Outcome: ERB group significantly lower rectal wall volume exposed to high doses. Late rectal toxicity G1: ERB- 58% vs. ERB+ 21%; G2 4% vs. 0%; G3 4% vs. 0%. Overall G1+ rectal toxicity 67% vs. 21% (SS)
 * Endoscopy: Telangiectasia ERB- vs ERB+ @ 6 months 16% vs. 24%; 1 year 45% vs. 28%; 2 years 39% vs. 24% (SS). High grade telangiectasia @ 1 years 20% vs. 10%; 2 years 19% vs. 9% (SS). Significantly less high grade telangiectasia at lateral and posterior part of Rwall
 * Conclusion: ERB reduced rectal wall volume exposed to >40 Gy, resulting in reduction of late mucosal changes and reduced late rectal toxicity

 * Nijmegen, The Netherlands
 * 2009 PMID 19523704 -- "Anal wall sparing effect of an endorectal balloon in 3D conformal and intensity-modulated prostate radiotherapy." (Smeenk RJ, Radiother Oncol. 2009 Jun 10.)
 * Treatment planning. 24 patients, 2 planning CTs (ERB-, ERB+), 3D-CRT and IMRT plans generated, dose 78 Gy. Anal wall contoured
 * Outcome: ERB+ significantly reduced D(mean), D(max), and V30-V70 for both 3D-CRT and IMRT plans.
 * Conclusion: ERB showed significant anal wall sparing effect
 * 2005 PMID 16168848 -- "Rectal wall sparing effect of three different endorectal balloons in 3D conformal and IMRT prostate radiotherapy." (van Lin EN, Int J Radiat Oncol Biol Phys. 2005 Oct 1;63(2):565-76.)
 * Prospective. 20 patients, 4 planning CTs, with comparison of 3 endorectal balloons: no ERB, ERB1, ERB2, and ERB3 inserted. 3D-CRT and IMRT planned to 78 Gy
 * Outcome: ERBs tolerated well. ERBs resulted in reduction of Rwall exposed to intermediate and high doses
 * Conclusion: ERB showed significant rectal wall sparing effect

 * Harvard
 * 2006 PMID 16584760 -- "A prospective evaluation of rectal bleeding after dose-escalated three-dimensional conformal radiation therapy using an intrarectal balloon for prostate gland localization and immobilization." (D'Amico AV, Urology. 2006 Apr;67(4):780-4. Epub 2006 Apr 11.)
 * Phase II. 57 men, at least one high-risk feature (PSA >10, GS 7+, T3). 3D-CRT to 75.6 Gy, rectal balloon for first 15 treatments. ADT. Median F/U 1.8 years
 * Outcome: V70 3.7 cm3
 * Toxicity: 2-year G3 rectal bleeding 10%; if anticoagulants 100% vs no anticoagulants 0% (SS). Controlled with APC
 * Conclusion: Dose-escalation with rectal balloon no measurable G3 rectal bleeding, unless patient on anticoagulants
 * 2004 PMID 15271308 -- "Impact on rectal dose from the use of a prostate immobilization and rectal localization device for patients receiving dose escalated 3D conformal radiation therapy." (Sanghani MV, Urol Oncol. 2004 May-Jun;22(3):165-8.)
 * Treatment planning. 28 patients. 3 plans: no balloon, boost (15 fractions), or entire course (40 fractions). RT 75.6 Gy
 * Outcome: V70 25% vs. 7% vs 4% (SS)
 * Conclusion: Rectal toxicity could be minimized through use of rectal balloon

 * Baylor; 2005 PMID 15749008 -- "Rectal wall sparing by dosimetric effect of rectal balloon used during intensity-modulated radiation therapy (IMRT) for prostate cancer." (Teh BS, Med Dosim. 2005 Spring;30(1):25-30.)
 * Retrospective. 116 patients, IMRT 76/35 @ 2.17 Gy/fx. Rectal balloon 100 cc air. Film phantom to simulate 4cm air cavity created by rectal balloon. Median F/U 2.6 years
 * Dosimetry: Dose reduction by 15% at distal air-tissue interface, 8% at 1 mm, and 5% at 2 mm. Coverage of posterior prostate wall comparable
 * Clinical: Late GI toxicity G1 10%, G2 7%, and G3 2%, no G4. DVH analysis average V70 13%, all <25%
 * Conclusion: Rectal balloon reduced anterior, posterior, and lateral rectal wall sparing. Late rectal toxicity low

Perirectal fat injection

 * Oviedo, Spain
 * 2009 (2005-2006) PMID 19213607 -- "Transperineal injection of hyaluronic acid in the anterior perirectal fat to decrease rectal toxicity from radiation delivered with low-dose-rate brachytherapy for prostate cancer patients." (Prada PJ, Brachytherapy. 2009 Apr-Jun;8(2):210-7. Epub 2009 Feb 12.)
 * Randomized. 69 patients with low/intermediate PCA, treated with I-125 brachytherapy to 145 Gy. Median prostate volume 35 cc. Arm 1) control vs Arm 2) transperineal perirectal fat injection. Endoscopic follow up. Median F/U 1.5 years
 * Outcome: Endoscopic mucosal damage control 36% vs. HA injection 5% (SS), rectal bleeding 12% vs 0% (SS)
 * Conclusion: Increased distance resulted in smaller rectal dose, less mucosal damage, and no rectal bleeding
 * 2007 PMID 17707267 -- "Transperineal injection of hyaluronic acid in anterior perirectal fat to decrease rectal toxicity from radiation delivered with intensity modulated brachytherapy or EBRT for prostate cancer patients." (Prada PJ, Int J Radiat Oncol Biol Phys. 2007 Sep 1;69(1):95-102.)
 * Retrospective. 27 patients treated with IMRT + HDR boost. Transrectal hyaluronic acid injection to perirectal fat under U/S guidance to create 1.5 cm space between rectal wall and prostate. Urethral and rectal TLDs placed during HDR
 * Outcome: No toxicity from HA injection, no change or migration at 1 year. Mean distance between rectum and prostate 2.0cm along entire length of prostate. Median rectal TLD dose decreased from 47% of urethral dose to 39% (SS), and from 7.1 Gy to 5.1 Gy during 11.5 Gy HDR boost
 * Conclusion: Increased rectum-prostate distance significantly decreased rectal dose during HDR brachytherapy

Management

 * Please see the diarrhea page
 * Please see the proctitis page

title: Radiation Oncology/Toxicity/Rectum


text:
User talk:S.M. Faisal

Welcome to Wikibooks, S.M. Faisal! – Mike.lifeguard  | talk 15:29, 26 April 2008 (UTC)

license: Creative Commons - Attribution Share-Alike - https://creativecommons.org/licenses/by-sa/4.0/

title: User talk:S.M. Faisal


text:
Radiation Oncology/Toxicity/Kidney

Kidney RT Tolerance

Spare 2/3 of one kidney.

 * Willett et al, 1986 - PMID 3759586 — "Renal complications secondary to radiation treatment of upper abdominal malignancies." Willett CG et al. Int J Radiat Oncol Biol Phys. 1986 Sep;12(9):1601-4.
 * Retrospective. Looked at 86 pts who received > 26 Gy to 50% of one kidney. Minimum 1 yr f/u. Creatinine clearance based on the Cockcroft formula.
 * Mean % decrease in GFR was 10% if only 50% of a kidney irradiated and 24% if 90-100% of one kidney was irradiated.

title: Radiation Oncology/Toxicity/Kidney


text: Punjabi

title: Punjabi


text:
Talk:US Tort Law

Title
Perhaps this should be named simply "Torts"? - Anonymous Dissident  Talk 16:41, 26 April 2008 (UTC)

title: Talk:US Tort Law


text:
User talk:Yuyu

Welcome, Yuyu temp!

Come introduce yourself at the new users page. If you have any questions, you can ask there or contact me personally. --Whiteknight (Page) (Talk) 17:34, 26 April 2008 (UTC)

Rename Request
Hello,. I've received your rename request. Here is what I need from you:

Once you have satisfied these requirements, send me a message and I can rename you. If you have any questions, or if you need any help, you can ask me on my user talk page, or you can ask the community at WB:CHAT or WB:AN. --Whiteknight (Page) (Talk) 17:34, 26 April 2008 (UTC)

title: User talk:Yuyu


text:
Talk:Punjabi

Help Improve this book.
This Wikibook has been created to help readers learn Punjabi. Readers are requested to suggest improvements and submit materials for early completion of the book and making the book useful to the reader. Thanks in anticipation

jaspal 12:22, 3 May 2008 (UTC)

Pronunciation of Punjabi words
This book is meant for non-native learner of Punjabi language. I have tried to give romanised (i.e. in roman letters) pronunciation of Punjabi words. The advantage of such an approach, I thought would be ease of the reader and his guaranteed familiarity with the system. But I have not been able to acheive any amount of consistency for obvious reasons. I have been weighing various other options. One such option is to straight away adopt IPA. The other option is to fix the use of various roman letters for both Punjabi vowels and consonants and then retain the romanised pronunciation. I invite one and all to guide me in this behalf.

jaspal 14:04, 7 May 2008 (UTC)

 * Gurmukhi is a near phonetic script. If someone has to learn IPA, it will probably be a lot of effort. Will it not be easier to learn Gurmukhi straight away start using it for pronunciation as well? Jaspal Singh 17:24, 16 August 2008 (UTC)

 * I think you should use romanisation, but in the script tutorial you should additionally give IPA for those who are familiar with it, so that they get a better idea of how to pronounce things. And sound files would be really great, if you know a Punjab with a microphone. Junesun (talk) 20:19, 16 August 2008 (UTC)

Teaching Punjabi and teaching the script
Good job, this page is quite comprehensive! I am wondering though if you'd like to go a step further. For example, your description of the Gurmukhi script is probably better than what could be found in textbooks usually: you divide the letters into groups and even give exercises for practise. However, I found that the easiest way to learn a foreign script, a method that can reliably teach any alphabet within 2-4 hours and without any tedious repetition, is to introduce only one letter at a time whenever possible and to provide exercises in the shape of recognizable words. See for example the approach used in the Greek and Korean Wikibooks. I can assist you in developing similar lessons for the Gurmukhi script if you like.

As for teaching the language, it would be really useful to have full-fledged lessons, so that students get exposure to the language, the words and grammar in context and in manageable bites. If you are not sure how to go about this, I'd be glad to give you some pointers and assist you in developing a lesson plan. I am a professional lesson developer for GermanPod101.com and I've also created lessons and lesson plans for various other projects, including several Wikibooks.

Best wishes,

Judith - Junesun (talk) 15:51, 9 June 2008 (UTC) Dear Jaspal,

Its great work. However, the usage of the letters 'chhuchha' depicting 'chauffer' and 'phupha' depicting 'phone' are not correct. 'chhuchha' is used as in 'chhaan' i.e shade, where for chauffer the letter used should be 'susse pair bindi'. Similarly the 'ph' in phone is more softer and pronounced with open lips, where as 'phupha' in Punjabi is pronounced with the pursed lips.

 * Thanks whoever wrote this comment. I will make the correction shortly. But just in case somebody can suggest English words for illustrating these sounds that will be great. In anticipation.....

 * Jaspal Singh 18:37, 27 August 2008 (UTC)

 * Can ਛੈਵਰਲੇ (Chevrolet) be appropriate example of 'chhuchha' sound. In the present scheme of things ਵ, ਰ and ਲ are not introduced till lesson 5. But that will be a minor irritant if an english speaker learning Pinjabi can be helped understand this sound appropriately. Waiting for comments and advice. Jaspal Singh 05:48, 8 August 2009 (UTC)

Teaching Punjabi and teaching the script
Please accept my apologies for being late in reponding. I greatly value your suggestions and the offer of help. I also agree to your suggestion for introducing script letter by letter. I must also share my plan of dividing the book into three different parts containing script, the common situational talk and the grammar in that order. This however will take some time as I devote only my free time to this voluntry effort. You are welcome to make suggestions or may also edit directly into the book.

I request you to edit the Author section at the end of the book to incorporate your self as a coauthor.

I greatly value your offer and look forward to work with you.

Regards.

Jaspal Singh 18:11, 16 July 2008 (UTC)

 * Awesome! I created Punjabi/Writing lessons plan so we can coordinate planning for the script lessons. Please add any words you can think of there. I'll let you know when I have an idea for a general lesson plan (situational talk with grammar and vocabulary explanations, teaching the language one step at a time). Thanks so much for your good work! Junesun (talk) 20:57, 19 July 2008 (UTC)

 * Very good job on the re-write! You found a lot of helpful English words. I'm particularly impressed with "khaki" and "Kazakh" - finding words for the /kh/ sound is hard in any language. I tried the lessons and it's already much easier to study the letters now. What would help now:

Also, if you explained the vowels before the first lesson or before the second lesson, the lessons would be much easier, because students could spend all that time recognizing and thereby practicing the vowel sounds in every single word you present afterwards. If you come across a recognizable word that only contains letters that have been presented before, it's very useful to let the student guess the word - don't just tell him what it means. If the student has to actively think and decipher words himself, the letters will stick so much better; plus it's a success for him. This is the reason I recommended teaching letters in an order other than the traditional rows, because then you can always have the student guess the words. For example, start by teaching A and give "ah!" as an example. Then, teach N and let the student guess "Anna" (don't just say it's the name Anna, let him read for himself). Then, teach M and let the student guess "mama" and "Annam" and "Manama"... it's kind of like that game where you have a word, add one letter and make a new word, add another letter and make another word, and so on. This is certainly a big advantage when learning a new script. However, I also see that the rows allow for better comparison of similar sounds like kh and gh and ghh and the like, so it's not all bad. Junesun (talk) 19:28, 12 August 2008 (UTC)
 * diagrams of how to draw the letters
 * sound files to illustrate the pronunciation

 * Thanks! Your words of appreciation have been inspiration and the good advice a source of strength.
 * I have moved on to vocabulary module and written some lessons there. Once I am through or substantially through with that I will for sure come back to the script so that I can make use of your technique which I am impressed with. I am also thinking in terms of relegating the grammar module to an Appendix status like I found in the Chinese (Mandarin) wikibook so that I can create some reading (practice) lessons at a more prominent position. Regards. Jaspal Singh 18:21, 14 August 2008 (UTC)

Shahmukhi
As I understand, Punjabi is written in two scripts: Gurmukhi (Punjab, India), and Shahmukhi (Punjab, Pakistan). Maybe we could add the Shahmukhi or, if Pakistani Punjabi's vocabulary is too different than Indian Punjabi (because of probable increased Arabic/Persian word borrowings), you can specify that you are teaching Indian Punjabi. Just a suggestion. YoshiroShin (talk) 03:27, 27 July 2008 (UTC)

 * Thanks Yoshiro. I perfectly agree. I wish Shahmukhi could be added to this wikibook. However I will need some help from my friends from Pakistan to do that. I invite one and all to add Shahmukhi as a script in this wikibook. They can add words not likely to be found in vogue on Indian side of Punjab.

 * As of now I am rewritting the Gurmukhi script part of this wikibook as suggested by Junesun above and as soon as it is complete I will give a link to it from the main page of the book and I shall add comment suggested by you. Thanks again for interest in the book.
 * Jaspal Singh 17:07, 27 July 2008 (UTC)

Actually now that I think about it, I think it may be better to have two separate Wikibooks for Gurmukhi Punjabi and for Shahmukhi Punjabi because:
 * 1. It will probably get extremely crowded in this Wikibook if we had both in one;
 * 2. The vocabulary will be too different; and
 * 3. Grammar may also be altered to be Persian-like which would make this pretty much a different language. Take into account Hindi and Urdu: Urdu has plenty more Arabic/Persian loans, and sometimes utilizes Persian grammar (as seen in Qaumi Tarana ).

 * YoshiroShin (talk) 18:12, 27 July 2008 (UTC)

Yes, though I think Qaumi Tarana is not realy a Punjabi composition. In fact many people in India think that Punjabi spoken in Amritsar(in Punjab, India) is much more near Punjabi of Lahore(in Punjab, Pakistan) than Punjabi spoken in say Patiala. This is true also as same dialect of Punjabi namely Majhi is spoken in Amritsar and Lahore both being part of same Majha region of undivided India. I would therefore presume that as far as vocabulary is concerned there is not much difference between Punjabi spoken in Indian Punjab and Pakistan Punjab. But your other point seems valid that both scripts in one book may make it crowded. Regards, have a nice time.

Jaspal Singh 15:07, 28 July 2008 (UTC)

 * "Yes, though I think Qaumi Tarana is not realy a Punjabi composition." I guess you were being sarcastic there, seeing as I never said that Qaumi Tarana was a Punjabi composition, because that would be funny...................................................

 * But anyway, since you find one of my points valid, how 'bout you turn the page "Punjabi" into a page that links to "Gurmukhi Punjabi" and "Shahmukhi Punjabi", and then move everything on this page over to "Gurmukhi Punjabi"?

 * That way, both will be technically in the same book, and it will look really good to someone wanting to learn Punjabi. All he has to do is type in "Punjabi" in the search area, and then he will immediately have a choice of which Punjabi he wants.

 * I think it's a good idea.

 * YoshiroShin (talk) 00:53, 29 July 2008 (UTC)

My sincerest apologies if I have sounded sarcastic though I did not mean that. When I the wrote comment I thought you are suggesting that 'Shahmukhi Punjabi' is awfully different from 'Gurmukhi Punjabi'. By saying that Shahmukhi can be added to this wikibook what I realy mean is that Shahmukhi script can be provided as a separate part of this book. As I have emphasized earlier Pakistan Punjabi and Indian Punjabi are realy not two separate languages. Allow me to reiterate that vocabulary of language spoken on both sides of border is same though written in different scripts. Therefore it will be perfect to provide intructions on both scripts in one book, though in separate parts. But having said that the language spoken on both sides of the border is same, I wonder if it will be useful to have 'Gurmukhi Punjabi' and 'Shahmukhi Punjabi' separately. I have yet to convince myself about that. I was wondering if we can have a way out where by the same word or same rule of grammar etc. can be taught by giving both Gurmukhi and Shahmukhi versions of the word etc. Initially though it looks it will be too cumbersome. Just think about that.

Since you have taken the trouble and have shown interest in the book, I am giving here link to re-written Gurmukhi script part of the book, though it is still incomplete. Your comment shall be highly valued.

Jaspal Singh 14:28, 29 July 2008 (UTC)

 * How about on the main page, you place links to different sections on the book (a little like what they have at the Sanskrit Wikibook ), and at the beginning you can place a link to the "learning Gurmukhi" part and another to a "learning Shahmukhi part", and under those you can place links dividing up your language lessons and within those, sentences and words can be supplied in both Gurmukhi and Shahmukhi at the same time, and the reader can choose which to read while going through the book.
 * Another example showing this is at the Mandarin Chinese Wikibook . There, the author supplies Traditional and Simplified Chinese characters altogether in the same lessons and the reader can choose which he (or she) wants to follow.
 * Taking into account your (definitely probably correct) claim that Pakistani and Indian Punjabi have basically the same vocabulary, I think this is a better idea than the one I previously suggested.
 * What do you think?
 * Oh, and just to let you know, I don't know Punjabi, and I am actually studying Hindi, but I have an okay amount of knowledge of the Perso-Arabic script (for Urdu purposes) so I might be able to help out.
 * Therefore, I might try to add in some stuff once in a while, but the rest should be left to the Punjabi speakers (who know a lot more than I would about Punjabi). I'm just making some formatting suggestions.
 * YoshiroShin (talk) 18:25, 29 July 2008 (UTC)

Wonderful idea Yoshiro. I will be doing that in due course, providing a stub for Shahmukhi. Meanwhile if you can let me know if you approve of the re-written Gurmukhi script I shall be able to recast the book. Jaspal Singh 15:47, 30 July 2008 (UTC)

 * I actually like the format of the re-written Gurmukhi script very much. I think it's great.
 * YoshiroShin (talk) 18:46, 30 July 2008 (UTC)

Thanks for being with me and your word of appreciation. Hope to keep up dialog in future too. Will be back with stub for Shahmukhi. Have a nice time.

Jaspal Singh 16:49, 31 July 2008 (UTC)

Recasting this Wikibook
Based on the suggestions made by Judith - Junesun (talk) I have reworked the Gurmukhi script part of this wikibook introducing letters one by one and using example that are familiar to English knowing readers. YoshiroShin (talk) recommended that we should have Shahmukhi script as part of this book so that it is easier to serach. He himself is writing Shahmukhi lessons. I have recasted the other parts of the book. For better organization of the book the following format is being considered.

 * Punjabi Language & This wikibook
 * Writing System : Gurmukhi
 * Writing System : Shahmukhi
 * Language Lessons
 * Vocabulary
 * Grammar

Each of the above Sections/Parts of the book will have pages devoted to different lessons. Each page will contain links to all lessons contained in the Section/Part prominently displayed on it. Before actually recasting the book in the proposed format I seek suggestions to make the presentation of the book more meaningful.

Jaspal Singh 01:39, 7 August 2008 (UTC)

New Lesson
Hi, everybody. I have added one more module Vocabulary to this book and created first lesson viz., Numbers to it.

PS : Suggestions for improvement are welcome please.

Jaspal Singh 17:46, 12 August 2008 (UTC)

 * Cool so far. If I see anything that I could provide suggestions for improvement on, I'll let you know.

 * YoshiroShin (talk) 19:10, 12 August 2008 (UTC)

Question
Does the Punjabi/Vocabulary/Relations article just contains some of the Relations, or does it need to include every relation because there are some missing. --Gman124 (talk) 04:43, 5 February 2009 (UTC)
 * The lists on vocabulary pages are not exaustive. But you may please add more items to them if you think some more will be useful for readers or let me know which ones you want so that I can do it. -- Jaspal Singh 15:16, 22 February 2009 (UTC)

title: Talk:Punjabi


text:
Talk:Circuit Idea/How to Make Perfect Components

Here is the building "scenario" that my students from group 68b and I were using during laboratory excercise about the op-amp circuits with parallel negative feedback (op-amp inverting circuits). Circuit-fantasist (talk) 18:03, 26 April 2008 (UTC)

Lab 4: How to make perfect components by parallel NFB
Thursday, April 24, 2008, 16.45 h

Is the real diode a perfect component?

A forward voltage drop VF appears across a real diode when a current flows through it... What is this voltage drop - useful or harmful? Sometimes it is useful; other times it is harmful...

"Useful" examples. When we make voltage stabilizers, we need this voltage drop. In these cases we do all that is possible to create and increase this useful voltage drop appearing across various diode component: diodes, LEDs, zeners, multiple diodes connected in series...

"Harmful" examples. In other cases, when we use a diode as a switching element, we do all that is possible to remove and to remove this harmful voltage drop... Then we need an ideal diode without forvard voltage drop VF...

Making the simplest parallel diode limiter

Why do we connect a reasistor R between the input voltage source and the diode (load)?

What does the combination (VIN + R) represent? What is it?

Deriving the basic idea from our human routine
(write here all the situations in your daily routine where you have remove all the obstacles standing in your way:) Circuit-fantasist 06:36, 26 April 2008 (UTC)

Implementing the powerful idea into an electrical circuit

What have we actually done here? How does it operate? What is the final result?

The answer is amazing: we have made just... a piece of wire...?!? What do you think about this speculation? Is it always right? Circuit-fantasist (talk) 06:59, 26 April 2008 (UTC)

An op-amp acting as a varying voltage source
What can act as a varying voltage source in our electronic circuit? What can "help" the imperfect diode by adding so much voltage as it loses across the diode? At last Lab 3 we were using transistors for such a purpose; let's now, for the sake of change, use an op-amp...

Now the op-amp has to "insert" the "helping" voltage VF into the circuit; so, how to connect it?

Finishing the op-amp circuit
Eureka! We have invented an (almost) ideal diode without (any) forvard voltage VF!

...multiple diode voltage drops...

...zener diode voltage drop...

...resistor voltage drop
With the same success we can destroy the "harmful" voltage drop across a resistor. What a circuit can we "invent" in this way? Write its name here....

Making the harmful voltage drop act as an input

Generalizing the powerful "helping" idea

We are already true magicians as we can transform any imperfect component into an almost ideal one! In this lab, we have transmuted a real diode (ordinary, LED, zener, any combinations of them, etc.), a resistor and a photoresistor into... a piece of wire:) having no any voltage drop across it! But with the same success we can make a "botomless" capacitor (an op-amp inverting integrator)... For this purpose, we just incorporate a varying battery to the imperfect component that compensated the losses inside the component. All the op-amp inverting circuits exploit this clever trick.

Resources
How do we create a virtual ground? is a circuit story about the great phenomenon. Op-amp inverting current-to-voltage converter reveals the basic idea behind the famous circuit. How do we build an op-amp ammeter? is a similar story about the active ammeter.


text:
Radiation Oncology/Toxicity/Pituitary

Hypothalamus-Pituitary Axis RT Tolerance

 * Childhood Cancer Survivor Study; 2009 (1970-1986) PMID 19364965 -- "Fertility of female survivors of childhood cancer: a report from the childhood cancer survivor study." (Green DM, J Clin Oncol. 2009 Jun 1;27(16):2677-85. Epub 2009 Apr 13.)
 * Retrospective. 5,149 femarle CCCS 5-year survivors not surgically sterile and cohort of 1,441 randomly selected female siblings
 * Outcome: RR for ever being pregnant 0.81 (SS)
 * Negative predictors: hypothalamic/pituitary RT dose >=30 Gy (RR 0.61), ovarian/uterine RT dose >5 Gy (RR 0.56) or RT dose >10 Gy (RR 0.18), treatment with lomustine or cyclophosphamide, or summed alkylating agent dose (AAD) 3-4
 * Conclusion: Fertility decreased among female pediatric cancer survivors

 * St. Jude Hospital; 2008 PMID 18309946 -- "Endocrine outcomes for children with embryonal brain tumors after risk-adapted craniospinal and conformal primary-site irradiation and high-dose chemotherapy with stem-cell rescue on the SJMB-96 trial." (Laughton SJ, J Clin Oncol. 2008 Mar 1;26(7):1112-8.)
 * Prospective trial (SJMB-96). 88 children treated with risk-adapted CSI and conformal primary site RT. Median CSI dose for average risk 23.4 Gy, for high risk 39.6 Gy
 * Outcome: 4-year incidence of growth hormone deficiency 93%, adrenocorticotropic hormone deficiency 23%, primary hypothyroidism 65%.
 * Dose-response: Only for hypothyroidism: <42 Gy 11% vs. >=42 Gy 44% (SS)
 * Conclusion: Pediatric patients with CNS tumors at high risk for treatment-related hormone problems; RT dose >42 Gy associated with increased risk of hypothyroidism

title: Radiation Oncology/Toxicity/Pituitary


text:
Permaculture Design/How to/Planting plans/A planting plan for Dunedin New Zealand

About Dunedin

Please add to this plan. Add links to the Wikipedia or Wikispecies articles abut each pant. Add comments and information about the seasons and the characteristics of the plants.

January
Brassicas ~ broccoli, cauli, kale, cabbage~ last planting of seeds. All salad types. Winter japanese radish, european radish endive & raddichio. Carrots for a july harvest

February
Chinese cabbage, tall pak tsoi, daikon radish, mescalun, chinese mustard, last planting of fennel & rocket. Spinach, turnip, onions for winter standing. Winter lettuce ~ cos, webbs wonderful ,imperial (for under cloches later)

March
Parsley. Last silverbeet. Plant green manure crops. Mescalun, rocket winter radish, turnips, raddichio, lettuce, carrots

Late April
Sow “greenfeast” peas in well drained soil broad beans – long pods best

May
Broad beans

June
Sprout seed potatoes inside. Later garlic, shallots, jerusalem artichokes.

July
Mustard & cress, mescalun (small warm spot or under cloche on windowsill) plant lettuce, parsley, silverbeetseeds in trays indoors. Garlic & shallots

Late July August
Cabbage, broccoli, peas, broad beans. early potatoes under mulch. More lettuce. Small early planting of zucchini. small sowing outside of carrots, radish, early turnips, mescalun, corn salad, silverbeet, spinach. Other outside sowings of onions, leeks, parsnips, celery garlic & shallots still ok.

September
Peas, broad beans, spinach, silver beet, carrots, radish. turnip, potatoes, broccoli, cauli, fennel. spring onions, lettuce, zucchini, brussel sprouts, celery cucumber. Late September beetroot, french beans, scarlet runner beans, kohl rabi, salsify

October
Last chance for parsnips. Sweet corn, celery, coriander, all salad types, turnips, carrots, broccoli, cauli, potatoes, parsley, yams, late spuds. Autumn sowings for brussel sprouts, silver beet, swede & fennel.

November
All salad types, late sweet corn, carrots etc. Broccoli, cabbage, cauli, kale, nz spinach, leek seedlings outside.

December
Peas. all salad types. Carrots, broccoli, cabbage, cauli, kale, french beans, turnips. Parsley & spinach. Kohlrabi.


text:
Permaculture Design/How to/Planting Calendars

At this stage, these planting Calendars are intended to help new comers to an area start planting productively. In that regard, the plants listed are common, generally well known, tested by many in that area. If you would like to develop a plan for your area, introduce yourself to a planting community and make notes on what they say. Start your calendar here and help us build plans for many regions.

 * /Dunedin New Zealand/
 * /Darwin Australia/


text:
IB Psychology/External Assessment/Paper 2

In Paper 2 of the external assessment, a list of twenty-one questions is given, three questions for each of the four options. Higher level candidates are to pick two questions, each from a different option, and they are allotted two hours to respond to both questions. Standard level candidates are to pick one question, and they are allotted one hour to answer the question. For both levels, Paper 2 represents 25% of the candidate's final Psychology grade.


text:
C++ Programming/Code/Standard C Library/Functions/tan

tan
The tan function returns the tangent of arg, where arg is given in radians. If arg is infinite, tan will return NAN and raise a floating-point exception.

 * Related topics: acos - asin - atan - atan2 - cos - cosh - sin - sinh - tanh


text:
C++ Programming/Code/Standard C Library/Functions/tanh

tanh
The function tanh returns the hyperbolic tangent of arg.

 * Related topics: acos - asin - atan - atan2 - cos - cosh - sin - sinh - tan


text:
C++ Programming/Code/Standard C Library/Functions/exp

exp
The exp function returns e (2.7182818) raised to the argth power.

 * Related topics: log - pow - sqrt


text: User talk:71.75.10.103

title: User talk:71.75.10.103


text:
User:OhanaUnited

I am Andrew, currently in the Master of Environmental Science (M. Env. Sc) program offered by University of Toronto's School of Graduate Studies at University of Toronto Scarborough.

I'm an administrator on English Wikipedia and bureaucrat on WikiSpecies. If you need help on these 2 projects, just drop me a message in my talk page (preferably in the corresponding project's talk page which you require help on).

title: User:OhanaUnited


text:
User:Wesley Gray/monobook.js

import_script('User:Whiteknight/gadgetscore.js'); import_script('User:Whiteknight/categorize.js'); import_script('User:Whiteknight/designer3.js');

title: User:Wesley Gray/monobook.js


text:
User:RogueMad

=Welcome= Hi! I'm RogueMad!

At the moment i'm making my homepage so it's kinda crumbly at the moment.

title: User:RogueMad


text:
User talk:RogueMad

I am a master at Need for Speed Carbon and Ratchet:Gladiator.Ask me something if you need help on anything.I'm also good at other things so you can ask me it.

Welcome!
Welcome, RogueMad!

Come introduce yourself at the new users page. If you have any questions, you can ask there or contact me personally.--- Anonymous Dissident  Talk 05:01, 27 April 2008 (UTC)

title: User talk:RogueMad


text:
Solved Question Papers - IIT JEE/MathsQP1996

IIT JEE MATHEMATICS QSN Let A={0,1,2,3,4,5,6,7,8,9} Exhibit the set B={X|X € A and x is even}& set C={X|2X € A }by listing memebers of B & C

Next qsn The angle between the pair of tangents drawn from a point P to a circle x^2+y^2+4x-6y+9sin^2 (A) +13cos^2 (A)=0 is 2A. Then the equation of locus of point P:

Next qsn An ellipse has excentricity 1/2 and one focus S (1/2,1). Its one directrix is common tangent (nearer to S) to circe x^2 +y^2=1 and x^2-y^2=1. Then equation of ellipse in standard form is_____


text:
Talk:Adventist Youth Honors Answer Book/Recreation/Pioneering

Transportation section
I find it ironic that an image of a Mormon wagon train is being use here. -- 208.81.184.4 (talk) 17:45, 27 March 2009 (UTC)


text: User talk:193.75.63.253

title: User talk:193.75.63.253


text: User talk:4.158.144.27

title: User talk:4.158.144.27


text:
Talk:A-level Chemistry/OCR/Atomic Structure

did the atomic number is changed when the atom is changed to ion?Explain.


text:
User talk:Yep fad

Welcome, Yep fad!

Come introduce yourself at the new users page. If you have any questions, you can ask there or contact me personally. --Whiteknight (Page) (Talk) 14:35, 27 April 2008 (UTC)

title: User talk:Yep fad


text:
Radiation Oncology/Health Technology Assessment

Health Technology Assessment

 * Subpage: Cost-Effectiveness
 * Subpage: Proton HTA

 * Wisconsin; 2008 PMID 18237799 -- "Randomized controlled trials in health technology assessment: overkill or overdue?" (Bentzen SM, Radiother Oncol. 2008 Feb;86(2):142-7. Epub 2008 Jan 30.)

 * Mt Vernon Hospital; 2004 (UK) PMID 14751499 -- "High-tech in radiation oncology: should there be a ceiling?" (Bentzen SM, Int J Radiat Oncol Biol Phys. 2004 Feb 1;58(2):320-30.)


text:
MediaWiki:Common.js/RandomBook.js

/* Random Book Finder, version [0.0.4a-r3] Originally from: http://en.wikibooks.org/wiki/User:Splarka/randbook.js Based roughly on http://en.wikibooks.org/w/index.php?title=MediaWiki:RandomBook.js&oldid=1209572 by Darklama.

Notes:
 * Grab only 10 random pages in one go because that is the limit.
 * 2 iterations may be needed because 10.5% of pages are books.
 * Refer to books by their ID to find them even when moved.
 * Append links instead with: mw.config.set( 'random_book_list', true ); (add this in your Special:MyPage/common.js);

$(document).ready( function($) {	var	reqid = 0, random_list = mw.config.get( 'random_book_list', false ),		randbookLink = mw.util.addPortletLink( 'p-navigation', '#', 'Random book', 'n-randbook', 'Show me a random book', 'x' ),		bookLink = mw.config.get( 'wgServer' ) + mw.config.get( 'wgScript' ) + '?curid=';

function fetch_categories( id, callback ) { $.getJSON( mw.util.wikiScript( 'api' ), {			format:		'json',			action:		'query',			prop:		'categories',			cllimit:	100,			generator:	'random',			grnnamespace:	'0|110',			grnlimit:	10,			requestid:	id		}, callback ); }

function showRandBookCB(obj) { var pages;

if ( !obj.query || !obj.query.pages ) { $(randbookLink).append(' error '); if ( random_list ) { removeSpinner( 'randbook' ); }			return; }

pages = $.map( obj.query.pages, function(page, id) {			return $.map( page.categories || [], function( cat ) { if ( cat.title.indexOf( 'Category:Alphabetical/' ) === 0 ) { return { id: id, title: page.title }; }			});		});

if ( !pages.length ) { // didn't find any, try again ++reqid; fetch_categories( reqid, showRandBookCB ); return; }

if ( !random_list ) { window.location.assign( bookLink + pages[ Math.floor( Math.random*pages.length ) ].id ); return; }

removeSpinner( 'randbook' ); $.each( pages, function {			$(randbookLink).append('  \u2022\u00A0' + this.title + ' ');		}); }

$(randbookLink).click( function(e) {		if ( random_list ) {			injectSpinner( this, 'randbook' );		}		++reqid;		fetch_categories( reqid, showRandBookCB );		e.preventDefault;	}); });

title: MediaWiki:Common.js/RandomBook.js


text:
Talk:X86 Disassembly/Variables

"Static" Local Variables
The line "This shows that the Microsoft C compiler creates static variables in the .bss section." is not 100% correct. While the variable is indeed in the  section in the case used as an example, Visual C++ (the C/C++ compiler) operates on very slightly more complex logic:
 * If the static variable is initialised to a non-zero value, it is placed in the  segment.
 * Otherwise, the variable is placed in the  segment.

This can be observed by compiling a simple source file with

will be in its function's  segment, while   (and   in C++) will be in the   segment.

Also note that in, an additional variable  , of type   , was created to act as a static guard. A static guard of this sort appears to be automatically generated whenever a local static variable is dynamically initialised, and only when a local static variable is dynamically initialised; to my knowledge, it will always be ,   , and non- /.

24.222.178.254 (discuss) 20:28, 28 April 2016 (UTC)

Global Variables
To avoid confusion, I think "Global Variables" should not be on the main page until the section includes some content. Shnizzedy (talk) 18:05, 27 April 2008 (UTC)

title: Talk:X86 Disassembly/Variables


text:
User:Shnizzedy

My User Pages at Various Wikis

 * Homestar Runner Wiki
 * This Might Be A Wiki
 * WikiBooks
 * Wikipedia
 * Wiktionary

Other Pages About Me

 * My Last.fm page
 * My ORCiD

title: User:Shnizzedy


text:
Talk:Transferring Data between Standard Dial-Up Modems

Questioning whether this works
Does this actually work? I was skeptical but decided to try it with a Windows 95 laptop and Ubuntu server. I got to the "Set them both up to use your modems" step, which doesn't to work, but for HyperTerminal (or any telecom communications program) to use your modem, it has to have a dial tone... Maybe I'm missing something... --Iamunknown 18:26, 27 April 2008 (UTC)

...you can set the modem to ignore no dial tone

Missing info
At the time of this writing, this page seems to be missing some information that I would consider to be mandatory. Before trying to use ATD, use either ATX3 (or on a line by itself), or combine them into ATX3D (AT = attention, X3 = use blind dial when dialing, D meaning to dial). Using X3 is mentioned by [CyberPillar ] [: dial-up modems], but since I'm the webmaster of that site, I won't bother to put that info into the main content area of this book. (I choose that simply to avoid self-promotion on a main Wikipedia content page.) I will add this last bit of related warning: If my memory serves me well, then this technique doesn't work with all modem equipment. When it doesn't work, the reason why may be rather challenging to determine. It might be that some modems work with this technique better than others? Or some phone cords? (The later claim of crossed cables being needed might help to explain this.) In other words: just because it works for you now, doesn't mean that it will work for someone else, or that it will work for you later in other circumstances. If it doesn't work, I would suggest trying to switch roles (which model is dialing and which is answering), as perhaps that might be helpful and it will probably be a fairly easy change (just typing different commands, and not needing to adjust physical wiring). On another side note, and possibly to do some more self-promotion in this Discussion section: This guide seems to expect people have HyperTerm. Other software ought to work as well: uses | TOOGAM's software archive: terminal software. I think that this topic (connecting via modems) may be quite worthy of a web page, but isn't sufficiently complex enough to warrant making so much material that it is worth being classified as a Wikibook. That's just my opinion, which admittedly may be rather ignorant. It could have been good info in the late 1990s and maybe even early this millennium, but the info is definitely using technology that is dated, now that people can get faster connections via CAT5, WiFi, and connections to cell phone towers. Using this technique would require using dial-up modems. Many of the modems out there may use older connectors (like an ISA connector to connect to the computer) which are found on fewer and fewer pieces of newer equipment. That is likely to only continue as newer equipment gets even faster bandwidth, and equipment that may be new today becomes cheaper over time. So this topic is largely becoming a historical novelty, at least where I'm at (in the USA), though I presume that will be true in more places around the world as technology keeps improving over time. By the way: I added a heading to the top discussion, which allowed it to show up in the table of contents. Hopefully that helps and doesn't bother anybody. 174.21.246.238 (discuss) 07:47, 30 December 2014 (UTC)

Something Wrong?
I got the right sound coming from the modem but they didn't seem to talk to each other. They timed out with "NO CARRIER" message.

Possible resolution?
Probably resolvable with X3 as I noted above in the Missing Info section. 174.21.246.238 (discuss) 07:47, 30 December 2014 (UTC)

Confirmed
It works! With Windows Vista to Windows '98, two 56k dial-up PC card and PCI card modems. But the rate had to be set really low, 40 bytes per second, though it will probably work much better repeatedly tried and reconfigured. Clark89 (talk) 05:16, 8 March 2009 (UTC)

Crossed or straight cable
What type should be the cable? I've read that most "wall socket <-> phone" cables are crossed. Or maybe it doesn't matter? I've tried crossed cable to directly connect modems but it haven't worked. --Piomar (discuss • contribs) 22:48, 31 March 2014 (UTC)


text:
User talk:Dekes12~enwikibooks

Welcome to Wikibooks, Dekes12! – Mike.lifeguard  | talk 19:48, 27 April 2008 (UTC)

Your account will be renamed
Hello,

The developer team at Wikimedia is making some changes to how accounts work, as part of our on-going efforts to provide new and better tools for our users like cross-wiki notifications. These changes will mean you have the same account name everywhere. This will let us give you new features that will help you edit and discuss better, and allow more flexible user permissions for tools. One of the side-effects of this is that user accounts will now have to be unique across all 900 Wikimedia wikis. See the announcement for more information.

Unfortunately, your account clashes with another account also called Dekes12. To make sure that both of you can use all Wikimedia projects in future, we have reserved the name Dekes12~enwikibooks that only you will have. If you like it, you don't have to do anything. If you do not like it, you can pick out a different name.

Your account will still work as before, and you will be credited for all your edits made so far, but you will have to use the new account name when you log in.

Sorry for the inconvenience.

Yours, Keegan Peterzell Community Liaison, Wikimedia Foundation 23:09, 17 March 2015 (UTC)

Renamed
 This account has been renamed as part of single-user login finalisation. If you own this account you can |log in using your previous username and password for more information. If you do not like this account's new name, you can choose your own using this form after logging in: . -- Keegan (WMF) (talk) 04:52, 19 April 2015 (UTC)

title: User talk:Dekes12~enwikibooks


text:
User talk:Janus god

Welcome to Wikibooks, Janus god! – Mike.lifeguard  | talk 19:48, 27 April 2008 (UTC)

title: User talk:Janus god


text:
User:Sdl6838

Proteomics: Corticosteroids

title: User:Sdl6838


text:
Cookbook:Lentil, Potato, and Tomato Curry

This creates a healthy, inexpensive and easy stew with depths of flavor. This recipe is fairly low on the heat scale, but feel free to add more cayenne pepper to up its spiciness. It is excellent served with chapatis or rice.

Ingredients

 * 1 cup red split lentils
 * 4 cups water
 * 1 teaspoon salt
 * 1 bay leaf
 * 1 tablespoon margarine
 * 1 tablespoon olive oil
 * 2 large potatoes, cut into ½ inch cubes
 * 1 teaspoon turmeric
 * ½ teaspoon cayenne pepper
 * 28 ounces canned diced tomatoes
 * 2 teaspoons garam masala
 * 1 teaspoon honey or sugar

Procedure

 * 1) In a large pot, combine and cook water, lentils, salt and bay leaf.
 * 2) In a large frying pan, combine potatoes, turmeric, cayenne pepper, and olive oil. Fry for 5–10 minutes.
 * 3) Add potato mixture to the pot with the lentils along with all remaining ingredients. Cook until the potatoes are soft and tender.
 * 4) Remove bay leaf before serving.


text:
Futurebasic/Language/Reference/usr

This function calls one of several low-level subroutines built into FB. The fnIndicator parameter indicates which routine to call; use one of the constants shown in the table below.

NEED IMAGE!!!!!

Example: One of the most useful USR functions is USR _fileAddr. You can use the LOCAL FN shown here to display information about an open file. LOCAL FN DisplayFileInfo(fileID) pbPtr& = USR _fileAddr(fileID) LONG IF pbPtr& <> _nil

Don't know what the print thing is

END IF

title: Futurebasic/Language/Reference/usr


text: User talk:67.86.217.138

title: User talk:67.86.217.138


text:
Futurebasic/Language/Reference/finderinfo

= FINDERINFO function =

Function
✔ Appearance ✔ Standard ✔ Console

Syntax
Move all waiting items to arrays or simple variables

Find out how many items are waiting to be picked up

Pick up an indexed item from the list

Gather a list of file spec records

Clear the list

Description
If the user launched your application by double-clicking a document icon, or by dragging document icon(s) to your application's icon, or by selecting document icon(s) and then selecting "Open" or "Print" from the Finder's "File" menu, then you can use the  function to determine which document file(s) were involved, and whether they should be opened or printed.

You should call  once, soon after your program starts. You should also check during null events to see if additional files have been added to the list. This can take place when an  event is sent from another application or when the user drags a file onto the icon of your running application.

•  - The result of the   function is one of the following:

Image was here.

•  - This variable is used to send a value to and receive a result from

Image was here.

The parameters for  are used to both send and receive values. In order to send a value of "1" for the count, you must first set the variable, then check it on return.

Image was here.

Note: Before your application can support Finder-launched documents, you need to set up certain special resources ( and  ) in your application's resource fork. Also,  will not work unless the "High-level event aware" flag is turned on in your application's   resource #-1. See the "Finder Interface" chapter in Macintosh Toolbox Essentials for more information.


text:
C++ Programming/Code/Standard C Library/Functions/log

log
The function log returns the natural (base e) logarithm of num. There's a domain error if num is negative, a range error if num is zero.

In order to calculate the logarithm of x to an arbitrary base b, you can use:

 * Related topics: exp - log10 - pow - sqrt


text:
Futurebasic/Language/Reference/folder

=FOLDER Function =

Function
✔ Appearance ✔ Standard ✔ Console

Revised
June 14, 2000 (Release 3)

Description
Depending on the parameters used, this function does several things with folders (directories). It can:

 Return a reference number for the current default directory. Return a reference number for a directory that you specify. Change the current default directory. Create a new folder. Return the parent volume

When  returns a reference number, it will either be a volume reference number (if the directory is a root directory), or a working directory reference number (if the directory is not a root directory). You can use this reference number to identify the directory when you use other FB statements such as.

This table summarizes the effects of the various parameter combinations. Note that when you use a nonzero number in, you can specify either a working directory reference number, a volume reference number, or a drive ID number. When you specify a volume reference number or a drive ID number, it represents the root directory on the specified volume.

Value returned

Get the reference number of the current default directory

"" (blank) zero

Reference number of current default directory

Get the reference number of the parent folder ":" (colon) any nonzero number Reference number of the parent folder. If no parent folder, it will return

Get a reference number for a directory relative to the current directory

partial path

zero

Reference number of specified directory, or zero if directory doesn’t exist

Get a reference number for an arbitrary directory

full path

zero

Reference number of specified directory, or zero if directory doesn’t exist

Change default directory

blank

non-zero reference number

Same number as

Create a directory relative to

partial path

non-zero reference number

If the path and  refer to an existing folder, its reference number

Create an arbitrary directory

full path

any non-zero number

If the path is invalid or path and  refer to an existing file, zero

Note: The reference number returned in  is a temporary number, which is only valid until your program quits. You cannot use this same number to refer to this folder at a later date. If you need to keep track of a file's location over time, create an alias record for the file.

title: Futurebasic/Language/Reference/folder


text:
C++ Programming/Code/Standard C Library/Functions/log10

log10
The  function returns the base 10 (or common) logarithm for. There will be a domain error if  is negative and a range error if   is zero.

 * Related topics: log


text:
Futurebasic/Language/Reference/exp

= EXP function =

Statement
✔ Appearance ✔ Standard ✔ Console

Description
Returns the value of the transcendental number "e" raised to the power of. The number "e" is the base of natural logarithms, and is approximately equal to 2.718281828. The  function is used extensively in probability theory and in applied sciences.

is the inverse of the  function; that is:   equals. always returns a double-precision result.

title: Futurebasic/Language/Reference/exp


text:
Futurebasic/Language/Reference/enterproc

= ENTERPROC statement =

Statement
✔ Appearance ✔ Standard ✔ Console

Syntax
Syntax 1:

Syntax 2:

Description
The  statement marks the beginning of a procedure block, which must end with an   statement. A procedure block is used to implement a function that uses the Pascal calling convention, which is a certain way that the function manipulates the stack. The most common use for this kind of function is to implement Toolbox "callback" procedures (often called "application-defined routines" in Inside Macintosh). Such callback procedures must use the Pascal calling convention.

An  procedure block can only appear within the "main" scope of the program; not within a. Each of the 's must be either a short (2-byte) integer variable or a long (4-byte) integer variable, or a   or   variable. The  can contain any collection of FB statements except another  ...  block (i.e., procedure blocks cannot be nested). The scope of all the variables referenced in the procedure block is either global (if the variable was declared earlier in a ...  block) or local to the procedure block itself.

A procedure block is called when some caller (typically a Toolbox routine) refers to the procedure's address in memory; your program can use the function to get that address. Typically, your program would pass that address to the Toolbox routine, to identify the procedure block as a "callback" procedure. When the procedure block is called,,  , etc. are assigned values which are passed by the caller. When the  statement is reached, control is returned back to the caller, and if   (or  ) was specified, its value is returned to the caller.

It's important that you know the number and types of parameters (if any) that the caller expects to pass to your procedure block, and that you set up the,  (etc.) parameters in the   statement accordingly. Likewise, you should know whether the caller expects your procedure block to return a value and, if so, whether the caller expects a 2-byte or a 4-byte value. If you use Syntax 1, you should specify a variable of the appropriate size in  if the caller expects a return value; otherwise you should omit. If you use Syntax 2, you should specify the name of a 2-byte or 4-byte type (such as  or  ) in the   parameter, and specify a   expression of that type, if the caller expects a return value; otherwise, you should omit the   and the. If you do not set up the input parameters and the return parameters correctly in your  and  statements, then your program is likely to crash when the procedure block is called. See Appendix C: Data Types and Data Representation, for a list of valid 2-byte and 4-byte variable types.

If you use Syntax 2, you can also execute a procedure block by using the  statement, although there is generally little reason to do this (it's usually better to use a   when you want to create a procedure that will be explicitly called by your program).

Note: When your program starts up, it will not automatically "skip over" the lines in a procedure block, the way it skips over the lines in a. In order to prevent your procedure block from being executed inadvertently, you should either branch around the procedure block using, like this:

or you should place the procedure block after an  statement, like this:


text:
Futurebasic/Language/Reference/exit

= EXIT <label> statement =

Statement
✔ Appearance ✔ Standard ✔ Console

Revised
January 2, 2001 (Release 4)

Description
This statement causes the program to jump to the statement following the indicated label. Unlike the  statement, the   statement makes sure that any loops,   blocks,  's, etc., that are being "jumped out" of get properly closed, so that the stack will be in a consistent state.

If an  is in the main program, the   must be inside the main. If an  is in a , the   must be inside the same. If an  is nested inside one or more   statements, the   must be after the last.

Any exceptions to the above conditions could result in substantial penalties or crashes.

title: Futurebasic/Language/Reference/exit


text:
Futurebasic/Language/Reference/exit case

= EXIT structure statement =

Statements
✔ Appearance ✔ Standard ✔ Console

Revised
May 30, 2000 (Release 3)

Description
When used inside a  loop,   conditional,   conditional, or in a   structure, this statement causes the program to jump immediately to the line following the ,  ,  , or  statement. This is useful when, you wish to break out of a loop because a certain condition has been met. is a safe way to do it.

Example:


text:
C++ Programming/Code/Standard C Library/Functions/pow

pow
The pow function returns base raised to the expth power. There's a domain error if base is zero and exp is less than or equal to zero. There's also a domain error if base is negative and exp is not an integer. There's a range error if an overflow occurs.

 * Related topics: exp - log - sqrt


text:
Talk:Marketing/Marketing Plan

There is no broken template...

It seems someone had inserted a category halfway up the article, and I confused it for a template. I have now moved it to the bottom of the document. The specified sub-category does not currently show, as there is not yet a marketing category. --James Chenery (talk) 05:11, 18 May 2009 (UTC)

Why is a Strategic Marketing Plan needed?

Since its inception, the Marketing Project has seen an amazing amount of creativity, discussion, and actual achievement. However, there have been frequent complaints that there has been no overall framework or context for this activity. This means it's not easy for newcomers to see where they can find a niche and make a contribution. There's also a danger that the same debates are repeated, rather than reaching an agreed position and being able to develop ideas in depth.

Dan

title: Talk:Marketing/Marketing Plan


text:
C++ Programming/Code/Standard C Library/Functions/sqrt

sqrt
The sqrt function returns the square root of num. If num is negative, a domain error occurs.

 * Related topics: exp - log - pow


text:
Futurebasic/Language/Reference/exit fn

= EXIT FN statement =

Statement
✔ Appearance ✔ Standard ✔ Console

Description
When used inside a  function, this statement causes the program to jump immediately to the   statement. The function then exits, passing back the value (if any) specified in the  statement. This is useful when, for example, you wish to break out of a loop and quit the function immediately;  is a safer way to do this than using something like.

Note: You should not use the  statement outside of a   function.

title: Futurebasic/Language/Reference/exit fn


text:
User:Xixtas/Counting Baby Animals/Six piglets

SIX Piglets


text: User talk:196.3.0.12

title: User talk:196.3.0.12


text:
Futurebasic/Language/Reference/rem

Syntax
REM

(')

(//)

"/*"

"*/"

Description
The REM statement (and its variations) provide a way for you to insert remarks into the source code which are ignored by the compiler. Remarks have absolutely no effect on how your program runs, but they can be very useful in helping readers to understand how your code works. If you use the REM keyword, or the apostrophe (') or double-slash (//) token, everything following it on the same line is treated as a remark; therefore, it's not possible to put a non-remark statement after remarks on the same line. The apostrophe and double-slash variations work identically to each other. In the FB Editor, remarks that begin with the apostrophe, the double-slash, or the "/*" token are automatically tabbed to the Remarks column of the Editor window if they're preceded by a statement. Remarks that begin with REM are not tabbed. When you use the "/*" and "*/" tokens, the "/*" indicates the beginning of the remarks, and the "*/" indicates the end of remarks. Because it uses two tokens, this variation allows you to do some things you can't do with other variations. Specifically: You can write remarks that span multiple lines, using only one pair of tokens.

For example: /* This is the first line of remarks. The remarks continue on this line. This is the last line of remarks. */ One disadvantage of using the "/*" and "*/" tokens is that you have to make sure you don't inadvertently include a "*/" token in the middle of your remarks. If you do, the compiler will assume that the remarks end there. For example: /* This is the first line of remarks. We have /*accidentally*/ put a remark-closing token in the middle of the remarks. When the compiler encounters this, it interprets the "*/" token following "accidentally" as the end of the remarks, and it attempts to compile the remainder of that line and the following line, leading to compile errors.

Note: You cannot put remarks after a DATA statement on the same line. Everything following the DATA keyword on the same line is considered part of the DATA statement.

title: Futurebasic/Language/Reference/rem


text:
Futurebasic/Language/Reference/rename

Syntax
RENAME

Description
Changes the name of a file or folder from the name specified in oldPath$ to the name specified in newPath$. The oldPath$ and newPath$ parameters are used along with refNum% and dirID& to determine the location of the item to be renamed: see Appendix A: Specifying Files and Directories, for more information. You cannot use RENAME to move an item into a different directory: oldPath$ and newPath$ must both refer to items in the same directory.

title: Futurebasic/Language/Reference/rename


text:
Futurebasic/Language/Reference/reset

Syntax
RESET

Description
This statement closes all files and devices that have been opened with the OPEN statement. RESET is functionally identical to using the CLOSE statement without any parameters.

title: Futurebasic/Language/Reference/reset


text:
Futurebasic/Language/Reference/resources

Syntax
RESOURCES

Revised
May 30, 2000 (Release 3)

Description
This is a non-executable statement that performs two main functions: It specifies your program's file type and creator; It identifies an existing file (pathname) containing resources that should be copied into the resource fork of your application file or code resource file, when FB builds your file. The RESOURCES statement is optional. If you don't include it in your program, FB builds an application file of type "APPL", with creator signature "xxxx", containing a standard set of resources. Resources may also be added by dragging a resource file into the project manager window. You can include multiple RESOURCES statements in your program. FB uses the first encountered RESOURCES statement to determine the file type and creator. The pathname parameter can be a full or partial pathname which specifies a file that contains resources; or which specifies an alias to such a file. If you use a partial pathname (for example, a simple file name), the path is assumed to be relative to your project folder. When FB builds your application file, it copies all the resources from the pathname file into the resource fork of the file that it builds. Note that if you don't specify the pathname parameter, you still must specify an (empty) pair of double-quotes. Using multiple RESOURCES statements It's sometimes convenient to have FB copy the resources from several different resource files. You can accomplish this by including multiple RESOURCES statements in your program, each specifying a different pathname parameter. If your program includes multiple RESOURCES statements, the second and all subsequent RESOURCES statements should not specify any parameter other than pathname. If your program includes multiple RESOURCES statements, there is the possibility of a "collision" between resources. This happens when a resource in one pathname file has the same type and same ID number as a resource in another pathname file. When this happens, the resource that was encountered later replaces the resource that was encountered earlier, when FB builds your file. You should keep this in mind when deciding in what order to place your RESOURCES statements. New feature in Release 3: If your resource has an ID of 32512-32767, the compiler will renumber it when it sees the conflict. That way, you can refer to it by name and pick it up with GETNAMEDRESOURCE. This is important for those that want to distribute source code with required resources.

Example: You have two resource files in your project.

myRes1.rsrc myRes2.rsrc myRes1.rsrc contains: _"PICT" ID 501  Name "One" _"PICT" ID 502  Name "Two" _"PICT" ID 32512Name "Fred" myRes2.rsrc contains: _"PICT" ID 501  Name "OneOne" _"PICT" ID 502  Name "TwoTwo" _"PICT" ID 32512Name "Barney" Your final application will contain: _"PICT" ID 501  Name "OneOne"<- Note that OneOne replaced One _"PICT" ID 502  Name "TwoTwo"<- Note that TwoTwo replaced Two _"PICT" ID 32512Name "Fred"  <- First version of 32512 saved _"PICT" ID 32513Name "Barney"<- Second version of 32512 renumbered Some useful resources

When building an application, FB automatically includes a standard set of resources that applications require. You can enhance your application by also including resources like the following (all of which can be created using ResEdit):

-VERS- "vers" resources with ID's 1 and 2 contain version information which is visible in Finder windows and in the "Get Info" window. See the "Finder Interface" chapter of Inside Macintosh: Macintosh Toolbox Essentials, for more information.

-SIZE- "SIZE" resources with ID's -1, 0 and 1 contain important information about your application's memory size, what kinds of events it can respond to, and more. FB always includes a "SIZE" resource whenever it builds an application, but you may want to override the features in the default "SIZE" resource by providing one of your own. See the "Event Manager" chapter of Inside Macintosh: Macintosh Toolbox Essentials, for more information.

-BNDL, FREF, ICN#- Use these resources to assign special icons to your application and to the documents that your application creates. These resources also determine what kinds of documents can be dragged to you application's icon in the Finder. See the "Finder Interface" chapter of Inside Macintosh: Macintosh Toolbox Essentials, for more information.


text:
Futurebasic/Language/Reference/restore

Syntax
RESTORE

Description
This statement is used in conjunction with the DATA and READ statements. It resets an internal pointer which tells FB where to find the next DATA item to read. This allows your program to READ the same DATA item(s) more than once if necessary. If you omit the expr parameter, the DATA pointer is reset to point to the first item in the first DATA statement. If you specify expr, the DATA pointer is reset to point to the item immediately following the expr-th item. Thus RESTORE 1 points to the second item; RESTORE 2 points to the third item; and so on.

Example: DATA Able, Baker DATA Kane, Dread DATA Echo FOR i = 1 to 5 READ x$  PRINT x$, NEXT PRINT RESTORE 3 READ x$, y$ PRINT x$, y$ program output: AbleBaker  KaneDreaEcho Dread Echo

title: Futurebasic/Language/Reference/restore


text:
Futurebasic/Language/Reference/return

Syntax
RETURN

Revised
October 2, 2000 (Release 4)

Description
You should include at least one RETURN statement in every subroutine that is called by a GOSUB statement. RETURN causes the subroutine to "exit"; that is, it causes execution to continue at the statement following the GOSUB that called the subroutine. You may also return to a specific location using RETURN "label". This pops the return address from the stack, then jumps to the requested address.

title: Futurebasic/Language/Reference/return


text:
Futurebasic/Language/Reference/rightstring

Syntax
subString$

RIGHT$(string$,numChars)

subContainer$$

RIGHT$$(container$$,numChars)

Revised
May 30, 2000 (Release 3)

Description
This function returns a string or container consisting of the rightmost numChars characters of string$ or container$$. If numChars is greater than the length of string$ or container$$, the entire string$ or container$$ is returned. If numChars is less than 1, an empty (zero-length) string is returned.

Note: You may not use complex expressions that include containers on the right side of the equal sign. Instead of using: c$$ = c$$ + RIGHT$$(a$$,10) Use: c$$ += RIGHT$$(a$$,10)

Example: PRINT RIGHT$ ("Nebraska", 3) program output: ska


text:
Futurebasic/Language/Reference/rnd

Syntax
randomInteger%

RND(expr%)

Description
This function returns a pseudo-random long integer uniformly distributed in the range 1 through expr&. The expr& parameter should be greater than 1, and must not exceed 65536. If the value returned is to be assigned to a 16-bit integer (randomInteger%), expr& should not exceed 32767. The actual sequence of numbers returned by RND depends on the random number generator's "seed" value; see the RANDOM statement for more information. Note that RND(1) always returns the value 1.

Example: To get a random integer between two arbitrary limits min and max, use this statement: randomInteger = RND(max - min + 1) + min - 1 (Note: max - min must be less than or equal to 65536.) To get a random fraction, greater than or equal to zero and less than 1, use this statement: frac! = (RND(65536)-1)/65536.0 To get a random long integer in the range 1 through 2,147,483,647, use this statement: randomInteger& = ((RND(65536) - 1)<<15) + RND(32767)

title: Futurebasic/Language/Reference/rnd


text:
Futurebasic/Language/Reference/run

Syntax
RUN

path$ [,refNum% [,dirID&]]

Description
This statement launches the application specified by path$, refNum% and dirID&, and puts it into the foreground, making it the active process. The program that launched the application does not quit, but is put into the background. See Appendix A: Specifying Files and Directories, to see how the path$, refNum% and dirID& parameters are interpreted.

title: Futurebasic/Language/Reference/run


text:
Futurebasic/Language/Reference/runtime

Syntax
RUNTIME

END RUNTIME

Description
The FB compiler has been created in such a way that it expects and calls upon specific functions located in the header folder. As an example, the statement WINDOW CLOSE wNum is routed to a runtime function named RUNTIME FBWindowClose(wNum&). A RUNTIME function behaves much like a local function, but the "RUNTIME" name indicates to FB that the function is part of the language. You may not add new syntax to FB by creating new RUNTIME functions. Only the compiler can make these calls. But you can modify these pieces of code as you would any source code. When all of the necessary headers have been compiled and FB is ready to begin examining your source code, the END RUNTIME statement tells FB that it no longer needs to track and record RUNTIME functions.

As you examine the RUNTIME functions, you may notice that only long integer parameters are used. This serves three purposes:

Long integers can be passed faster than any other type of parameter RUNTIME functions know in advance what type of parameter is expected. For instance, a RUNTIME function might expect a string pointer, but never a string. The use of long integers insures that variables will fall on long integer boundaries which greatly speeds the execution of PPC code.

title: Futurebasic/Language/Reference/runtime


text:
Futurebasic/Language/Reference/route

Syntax
To re-route text and graphics:

ROUTE [#]_toPrinter

ROUTE [#]_toScreen

ROUTE [#]_toBuffer [+ 0... 4 ]

To re-route text:

ROUTE [#]serialPort

ROUTE [#]fileID

Revised
May, 2001 (Release 5)

Description
This statement causes text printed by subsequent PRINT statements to be sent to the indicated device. If you specify _toScreen or _toPrinter, subsequent drawing commands are also sent to the indicated device. If you specify _toBuffer, only text printing commands are sent to the indicated device.

Using ROUTE_toPrinter: ROUTE _toPrinter opens a new print job unless a print job is already open. When you first open a new print job, the printer adopts the font and graphics characteristics that are in effect in the current screen window. Subsequent PRINT statements, as well as graphics commands such as BOX, CIRCLE and PLOT, are sent to the printer. Subsequent statements which affect the appearance of text and graphics, such as TEXT, PEN and COLOR, apply to the printed output. Subsequent QuickDraw Toolbox commands such as FRAMERECT apply to the printed output.

Note: To actually put out the current printer page, use the CLEAR LPRINT statement after sending text and drawing commands to the printer.

Using ROUTE_toScreen: After using ROUTE to direct output to the printer, or to a serial device or a file, you can use ROUTE _toScreen to re-direct output back to the screen window again.

Note: Statements which affect the appearance of text and graphics, such as TEXT, PEN and COLOR, apply separately to the screen window and to the printer. The settings in one device don't affect the settings in the other, except when you first open a new print job.

Using ROUTE serialPort and ROUTE fileID: These statements cause text printed by subsequent PRINT statements to be sent to the specified open device. They don't affect the destination of graphics commands. This group of statements: ROUTE deviceID PRINT itemList1 PRINT itemList2: PRINT itemListN

ROUTE _toScreen has the same effect as this group of statements: PRINT #deviceID, itemList1

PRINT #deviceID, itemList2: PRINT #deviceID, itemListN

Using ROUTE_toBuffer: You can use the FB ROUTE _toBuffer statement to print information directly to a handle. You may use any one of five handles by setting the route statement in the range of _toBuffer through _toBuffer + 4. When routed to a buffer, only text commands are sent to the handle. Graphic commands are ignored. Information printed to a buffer ends up in one of five handles stored as globals in the FB runtime. This array is named gFBbuffer(n) where n is a numeric expression in the range of 0...4. The following example prints text to buffer number 2.

ROUTE _toBuffer + 2, PRINT "Hello" PRINT "Goodbye" ROUTE _toScreen

When this snippet has been executed, gFBbuffer(2) will contain a handle that points to a moveable block of 14 bytes: HelloGoodbye Note that carriage returns are added or suppressed in writing to a buffer just as they would be in writing to a file or to the screen. If you want to dispose of a buffer, use DEF DISPOSEH.

DEF DISPOSEH(gFBbuffer(2)) FB Lite behavior: When you use the "FB Lite" runtime, built-in graphics statements such as BOX, CIRCLE and PLOT are always directed to the Graphics Window; using ROUTE _toPrinter won't cause such commands to be directed to the printer. If you want to send graphics to the printer while using "FB Lite," first execute ROUTE _toPrinter, then use QuickDraw Toolbox routines such as FRAMERECT, FRAMEOVAL, LINETO, etc.

Note: The WINDOW statement and the WINDOW OUTPUT statement implicitly execute a ROUTE _toScreen statement. Also, any user action which activates a screen window (such as clicking on its title bar) will implicitly cause a ROUTE _toScreen. If you want to make sure that output is not inadvertently directed to the screen window, you should check for _wndActivate events in your dialog-event handling routine, and re-direct the output as necessary.

title: Futurebasic/Language/Reference/route


text:
Talk:Digital Signal Processing/Windowing

"A nieve approach, the rectangular window, involves simply truncating the dataset before and after the window, while not modifying the contents of the window at all. However, as we will see, this is a poor method of windowing and causes power leakage."

nieve == naive?

power leakage == spectral leakage? I am far from being an expert but it seems to me that statisticians would talk about 'power leakage' but most dsp texts would refer to 'spectral leakage'. To an electronics person, spectral leakage makes a lot more sense.

A particular favorite reference is 'A Scientist and Engineer's Guide to Digital Signal Processing'. http://www.dspguide.com/ It is aimed at people who actually want to implement dsp. Most textbooks ignore spectral leakage. It's a major gotcha. If you don't know about it, your attempts at fft are doomed!


text:
Futurebasic/Language/Reference/if

Statement
Appearance 			Standard 			Console

Syntax
IF expr THEN {dest1|statement1 [:statement2 ...]} ¬ [ELSE {dest2|statement3 [:statement4 ...]}] dest1 and dest2 are either line numbers or quoted statement labels.

Description
Conditionally executes one or more statements, or jumps to an indicated line, based on the value of expr. If expr is evaluated as "true" or as nonzero, then the program either jumps to the line indicated by dest1, or it executes statement1, statement2, etc. If expr is evaluated as "false" or as zero, and you've included the ELSE clause, then the program either jumps to the line indicated by dest2, or it executes statement3, statement4, etc. Each of the statement's can be any executable statement except a "block" statement such as FOR, WHILE, DO, etc. expr can be either a numeric expression, a "logical" expression, or a string. A logical expression normally contains "data comparison" operators, and can be evaluated as being either "true" or "false." Here are some examples of logical expressions: x! > 19.7 myName$ = "RICK" 6*7 <= 42In FB, numeric expressions and logical expressions are interchangeable. When a numeric expression is used in the context of a logical expression, then it's considered "true" if it's nonzero, or "false" if it's zero. For example: IF x+3 THEN BEEP Here, the BEEP will be executed if and only if x+3 is not zero. When a logical expression is used in the context of a numeric expression, then it's evaluated as -1 if it's true, or as 0 if it's false. For example: found = (fileName$ = seekName$) Here, if fileName$ equals seekName$, the value -1 is assigned to found; otherwise, found is assigned a value of 0. You can use the operators AND, OR, NOT within expr. Note, however, that these three are considered to be arithmetic operators, not logical operators. This can lead to some unexpected results if you're not careful. For example, this expression: firstNumber& AND secondNumber& may evaluate to zero (false), even when both firstNumber& and secondNumber& are each nonzero (true). When you wish to use AND, OR, or NOT in the context of a logical expression, you should use operands which always evaluate either to -1 or to 0. For example: firstNumber& <> 0 AND secondNumber& <> 0 This expression behaves "logically," because (firstNumber&<>0) is always -1 or 0; and likewise (secondNumber&<>0) is always -1 or 0. The expr can also be a string. When a string is used in the context of a logical expression, it's evaluated as "true" if and only if the length of the string is greater than zero. Note: The IF statement is a one-line structure. To create a conditional structure spanning multiple lines, use the LONG IF statement. Use caution when comparing floating point values to zero or to whole numbers. The following expression may not evaluate as expected: IF x# = 1In this statement, the compiler compares the value in x# to an integer "1". Since SANE and PPC math both use fractional approximations of numbers, the actual value of x#, though very close to one, may actually be something like 0.99999999 and therefore render unexpected results.

title: Futurebasic/Language/Reference/if


text:
Futurebasic/Language/Reference/inc

Statement
Appearance 			Standard 			Console

Syntax
INC(intVar) intVar ++ numericVariable += IntegerValToAdd === Revised === May 30, 2000 (Release 3)

Description
This statement increments intVar by 1; that is, it adds 1 to the value in intVar, and stores the result back into intVar. intVar must be a (signed or unsigned) byte variable, short-integer variable or long-integer variable. If intVar is already at the maximum value for its variable type, then INC(intVar) will cycle it back to its minimum value. Example: INC(x&) and... x& ++ and... x& += 1 ...are equivalent to: x& = x& + 1 The following expressions are also equivalent. x& = x& + 100 x& += 100 Note: The += syntax may not be used for arrays of strings, containers, or records (though it may be used in the concatenation of simple strings or containers). Where arrays are involved, only numeric values may take advantage of this syntax. This syntax is valid for values other than 1.

title: Futurebasic/Language/Reference/inc


text:
Outdoor Education/Wishlist

 * 1) Copyright free images
 * 2) * Wikimedia Commons, a repository of freely-licensed media
 * 3) * flickr cc search
 * 4) Copyright free content
 * 5) * US Government sources (training manuals for the military etc)
 * 6) * Wilderdom provides free culture OE material
 * 7) Authors
 * 8) Editors
 * 9) Students to work on this as a project
 * 10) Reviewers

title: Outdoor Education/Wishlist


text:
Outdoor Education/Proposal

The niche
There is a fairly small range of textbooks on the topic of outdoor education, typically North American. These books regularly go out of print, thus much good material is lost to the community. The proposed concept for this wikibook is to harness the outdoor education community knowledge to create a combined open outdoor education textbook for use in secondary- and tertiary-level outdoor education training.

Where good quality, freely usable content already exists online (e.g., on university websites), this book may simply link to that material. However, the book also provides a way to host materials which make appropriate textbook content.

Over time, books and articles which are out of print and/or for which copyright permission allows, may be converted and uploaded, providing they fit with the book structure. Original, intact previous publications are, however, probably best uploaded to WikiSource. Content uploaded into wikibooks should be editable and modifiable.

What this book is

 * 1) An introduction to outdoor education.
 * 2) A free culture text which covers the major topics in outdoor education.
 * 3) Targetted for people studying outdoor education or training to be outdoor educators.

What this book is not

 * 1) Commercial
 * 2) Lessons plans - such content would be more appropriate on the accompanying outdoor education wikiversity page.

title: Outdoor Education/Proposal


text:
Futurebasic/Language/Reference/inc long

Statements
Appearance 			Standard 			Console

Syntax
INC {LONG|WORD|BYTE} (addr&) Description: This statement increments the long integer, short integer or byte which begins at the specified address in memory; that is, it adds 1 to the value in memory and stores the result back into the addressed location. If the long integer, short integer or byte is already at its maximum possible value, then the statement will cycle it back to its minimum value. Example: INC LONG (myAddr&) ...is equivalent to: POKE LONG myAddr&, PEEK LONG(myAddr&) + 1 Also: INC WORD (myAddr&) ...is equivalent to: POKE WORD myAddr&, PEEK WORD(myAddr&) + 1

title: Futurebasic/Language/Reference/inc long


text:
Outdoor Education/Contributors

 * 1) James Neill
 * 2) Mike.lifeguard
 * 3) Ian Boyle

title: Outdoor Education/Contributors