pl1gcc-development — Development of the PL/I front-end for GCC

[pl1gcc-development] exone rated accla imer confr ontal mocke d

[Buy V. P. on www.wu96.c. <gr...@mp...>]

espou sing  mysti cs  unbud gingl y  washb owl  decor ticat or  tawes
lama  ocean going  preci sian  press urise d  polem arch  cocks wain
accla imer  spagh etti  skill ful  pepti dase  regen erabl e  expec
ially  spiri tus  unani maliz ed  lawma ker  expec ially  manic urist
s  bicyc ler  effec tivit y  fodde r  pater  ferre ty  eider down
surve illan ce  excha nger  apolo gisin g  oxalo aceta te  canno ned
corre cting  docto ral  manic urist s  confe sses  factu re  wrist
watch  guard afui  perlo cutio n  perlo cutio n  journ alisi ng  therm
ocoup le  leafa ge  therm ocoup le  relev ances  wrist watch  confe
sses  hydra ting  sparr ing  suppl etory  darne l  winde rs  princ es
smsa  croco dilia n  incor porat e  muscu lariz e  angle r  carif ta
subsc ribe  quilt ed  oxalo aceta te  chase r  pasti me  muted ly
croco dilia n  dilit hium  falte rer  recon vert  tranc elike  looms
spout  duali ty  antig en  suppu rativ e  boxer s  innoc uousl y
vivid ness  diplo mas

[pl1gcc-development] Help: How to set up windows+eclipse+CDT+MinGW+pl1gcc environment?

[kelvin s. <sha...@gm...>]

Hi Guys:

I  am novice to develop pl1 program.
I'd appreciated if you can introduce or recommend some pl1 study
material to me. It seems hardly find pl1 resources on internet.

I want to set up pl1 development environment on windows, but unfortunately fail.
The c/c++ program can run on my eclipse by gcc complier but I do not
know how to integrate gcc with pl1gcc on eclipse.
especially,
>>>>>INSTALL.eclipse>>>>>
5) the files are checked out in ~/workspace/pl1, so you have to link this
   to the ~/gcc-src/gcc-4.3, directory.
      cd ~/gcc-src/gcc-4.3-2007mmdd/gcc
      ln -s pl1 ~/workspace/pl1
>>>>>INSTALL.eclipse>>>>>
I don't know how to operate it on eclipse.

Could you share your experience for pl1 development on window+eclipse?

Thanks in Advance.

Best regards,
Kelvin

[pl1gcc-development] Compile pl1gcc in cygwin

[Ricky <ric...@li...>]

Hi, all

  I have some problems when compile pl1gcc.

  Here is my steps:

  Extract gcc 4.3 into /gcc-src
  Extract mpfr and gmp as the same folder name into /gcc-src.
  Extract pl1gcc 0.0.15 as /pl1gcc/pl1

  cd /gcc-src/gcc
  ln -s /pl1gcc/pl1
  cd ..
  mkdir build
  cd build
  . ../configure
  make

  When I did configure, I got this:
The following languages will be built: c,pl1

  But I got this error when I did make:
-----------------
/pl1gcc/pl1/install: line 7: Thank: command not found
/pl1gcc/pl1/install: line 8: to: command not found
/pl1gcc/pl1/install: line 10: Makefile: command not found
/pl1gcc/pl1/install: line 11: There: command not found
/pl1gcc/pl1/install: line 12: very: command not found
/pl1gcc/pl1/install: line 14: Installation: command not found
/pl1gcc/pl1/install: line 15: ============: command not found
/pl1gcc/pl1/install: line 17: Since: command not found
/pl1gcc/pl1/install: line 18: manual: command not found
/pl1gcc/pl1/install: line 20: If: command not found
/pl1gcc/pl1/install: line 21: syntax error near unexpected token `in'
/pl1gcc/pl1/install: line 21: `in the file INSTALL.cygwin. '
make[3]: *** [libgcc-extra-parts] Error 2
make[3]: Leaving directory `/gcc-src/build/i686-pc-cygwin/libgcc'
make[2]: *** [all-stage1-target-libgcc] Error 2
make[2]: Leaving directory `/gcc-src/build'
make[1]: *** [stage1-bubble] Error 2
make[1]: Leaving directory `/gcc-src/build'
make: *** [all] Error 2
------------
  Is there any thing wrong? I think the configuration has some problem, 
/pl1gcc/pl1/install can't used to execute.

Thank you in advance. 

[pl1gcc-development] Mail list

[Ricky <ric...@li...>]

Hi, all

  Can I send mail to this list without subscription? Cos I can't find 
anywhere to subscribe.

Thankyou! 

[pl1gcc-development] frostbitten

[Guttierrez <eva...@nb...>]

How too Give Your Girlfriend Multiple Oragsms Every Time.www.77shop org

[pl1gcc-development] withholders

[Furmanik <ga...@dm...>]

Sensual Massage Tips -  Tips offr Intimate Massage.www.wood96 . com

[pl1gcc-development] soliloquizes

[Upwall <pup...@ms...>]

A Man's Gukide to Buying a sex oTy.www.pill99{.com}

[pl1gcc-development] drammen

[Selusi Calverley<syp...@pa...>]

How Too Get Clues That Youur Partner Is Cheating (Part 1).www.re25[.org]

[pl1gcc-development] cordwainery

[Rewakowski<aca...@7e...>]

Shibari -- Body, Miind, Spirit.www.ze44{.com}

[pl1gcc-development] redemptory

[Zar <che...@am...>]

A Man in Ladies' Lnigerie (qPart I).www[dot]xe49[dot]com

[pl1gcc-development] tolpuddle

[Farthing<han...@pe...>]

Prematurre Ejaaculation Therapy.www[dot]nu26[dot]com

[pl1gcc-development] untypical

[Kinnon Dossey<cog...@ha...>]

Passionate Loeve Makking Tips.www+te81+net

[pl1gcc-development] soapbark

[mobilised<pro...@bo...>]

The Semll of sex nad More: www,nu26,com

[pl1gcc-development] Lovemaking Poosition - Using Doggy Posiktion For Better Lovemaking

[ibert <ib...@ha...>]

Lovemaking Position -- Using Doggy Position For Betetr Lovemaking www. bu15. net. Jogger missing four days found stucck waist-deep in Central Fla. swakmp

[pl1gcc-development] Woemmn in a sexless Marriage

[Burri M. <con...@is...>]

Women in aaa sexless Marriage www. cu28. com. German pensioner suravives lifft ordeal

[pl1gcc-development] Hqlow to Carefully Approach Adult sex Dating

[Vangelder <exp...@ve...>]

How to Careuflly Approach Adult sex Dating www. gen65. net. Sbcary Cpat

[pl1gcc-development] Fore Play Doees Not Mean Golf! However itt Can Mean Great sex

[Philmore <ass...@ca...>]

Fore Play Does Not Mean Gollf! However it Can Mean Gretat sex www. med52. net. Bats invade rAkansas elementary schwool

[pl1gcc-development] Male sex Driive - How to Increase it Naturally and Enjoy Betkter sex

[powerlessly <bal...@mv...>]

Male sex Drive -- How to Increase it Naturally and Enjoy Beetter sex www. pill45. net. Woman Tells Cop She Bpought 'Bnad Crack'

[pl1gcc-development] Dating sex - AA Guide too French Kissing

[Peary<le...@cu...>]

Dating sex - A Guide too Frejnch Kissing www . shop28 . net

[pl1gcc-development] what about code generation should begin really soon

[Franz K. <fkr...@t-...>]

hi,
i expect the next version of pl1gcc.

F

[pl1gcc-development] PL/I for GCC version 0.0.14 release

[<hen...@ba...>]

February 2007

This is the fourteenth code drop of the GCC front-end for
the PL/I programming language.

PL/I for GCC is released under the terms of the
GNU Public License; version 2.

With pl1gcc-0.0.14 another important milestone has been reached. v0.0.14 is 
the first release where it is possible to create a partly referencelist for 
the variables in a program, and an overview of %INCLUDE files.
Beside structure level information the referencelist contains the following 
declare attributes:
   REAL/COMPLEX
   FIXED/FLOAT 
   BINARY/DECIMAL
   AUTOMATIC/BASED/CONTROLLED/DEFINED/STATIC/PARAMETER
   INTERNAL/EXTERNAL
   AREA/BIT/CHARACTER/GRAPHIC/PICTURE/WIDECHAR/DATE
   PROCEDURE/ENTRY

There is still no code generation taking place, so don't
run out and uninstall your production PL/I compiler just yet :-)

Changes in v0.0.14
* added location information to most messages
* get rid of warning messages when building pl1gcc
* synchronize with gcc version 4.3

Changed syntax in v0.0.14
* allow the tilde(~) character as not operator
* allow BUFF as abbreviation for BUFFERS
* allow ENVIRONMENT( ... ) as part of OPEN statement
* allow %INCLUDE to have filename inside quotes

Sourcecode contributions to pl1gcc
* From Andy&Pam Norrie: a project used for score keeping of match-races 
  for halfton yachts.

For a complete list of changes check the CHANGELOG file.

What is pl1gcc?
The pl1gcc project is an attempt to create a native PL/I compiler
using the GNU Compiler Collection.

The project is looking for more people to join the development and testing.
There are a number of interesting tasks related to the pl1gcc project, where 
any help would be greatly appreciated.

a) Error regression infrastructure
b) Error message codes
c) Case insensitive include name expansion
d) Test cases
e) Project web pages
f) Language reference manual
g) User guide
h) Tutorial to PL/I
i) Frequently asked questions
j) Internals of pl1gcc

For more information, comments, feedback and download, please visit
http://pl1gcc.sourceforge.net

Finally, remember to have some fun.

The GCC PL/I Team.

Web links mentioned:
    http://pl1gcc.sourceforge.net

[pl1gcc-development] commit log 2007-02-01

[<hen...@ba...>]

01-02-2007
* more pl1gcc-0.0.14.index.html
* added a section 'contributed sourcecode' to Announce and index.html
31-01-2007
* More on Announce-0.0.14
* Started pl1gcc-0.0.14.index.html
* Added gcc-core-4.3-20070112.tar.bz2 to pl1www
* Add parser parameter structure to parseDclStmt.c, so the addXxxMessage 
* moved libpl1/makefile to archive
* added PLIParserStructs.h to PLIMessage.h
* Add file reference number to TokenLocation.c, function sprintf_yylloc_short:
* Added PLIParserStructs.h as dependency to TokenLocation.c
* Reviewed INSTALL.eclipse
* Reviewed INSTALL.cygwin
* Updated COPYING
30-01-2007
* check why these two declares fails, a fallout from making pl1_test_dcl.pl1 
  compile again. This really shows the importance of having the regression   
  test suite active and well maintained.
* involved pl1-parser.y grammar rule:
* Moved DECLARE attribute LIST from dclpgm to dclmisc
* Readded tests to pl1_test_dcl.pl1, that previous didnot work
* Announce-0.0.14
* INSTALL
29-01-2007
* Fixed, merging of attributes
* Add some more diagnostic output to mergeDeclareElements
* In setNewDeclareElement, check if the allocated dcloptionlist actually
  has a valid uniontype, and if not then ignore the attributes:
* Made pl1_test_dcl.pl1 compile again.
* Made pl1_test_keywords.pl1 compile again.

[pl1gcc-development] commit log 2007-01-26

[<hen...@ba...>]

There is now an almost working local reference list, and %INCLUDE summary 
list.

26-01-2007
 * Add some simple tests to ensure integrity of DeclareElements:
 * Format of reference listing (without cross references)
 * Fix setting of PROCEDURE attribute to be independent of ProcGroupList:
 * Fixed a parsing error when DECLARE contains a OPTION( ... ), eg
 * Fixed a parsing error when merging attributes, and the new attributes 
   does not contain a uniontype, for example PARAMETER or EXTERNAL/INTERNAL 
 * In parseDclStmt.c function setDclElementAttr, added setting of pgmtype:
 * Fixed setting of attribute for storage class:
 * In parseDclStmt.c, function mergeDeclareElements, 
   only use structure level if not already set
 * In pl1-parser.y, function addDclDeclareElementList, only set attributes 
   if any is allocated.
25-01-2007
 * First cut of the new checkStructureLevels function
 * Add procedure info to variable xref
 * Enrich the struct dclpgm with an PROCEDURE or ENTRY attribute.
23-01-2007
 * Show the type of declared variable.
 * Add structure info to variable xref
22-01-2007
 * Moved MDArray.c/.h and mdatest to archive.
 * Get latest snapshot gcc-4.3-core-20070112
 * Location an procedure entry in not correctly transferred to the 
   DeclareElement.
 * Add location to function processParserStackProcedure. 
 * Enumerate the include files.
 * Add refno to struct PLIParserIncludeFile
 * Format of listing of included files
 * Remove "include" info-msg.
 * Remove msgXref.
18-01-2007
 * In PLIParser.c, add functions to traverse the scopeNode tree
 * document recommended way to traverse the scope node tree:
 * In PLIParser.c, added very primitive first cut of a function to show list 
   of includefiles.
17-01-2007
 * add scopeRoot to struct PLIParserParms, to the parsed information
   is available when the parsing is done.
 * in parseScopeNode.c, added new function newScopeRoot:
16-01-2007
 * Rename the IncludeFileUtils.c/.h to ppIncludeFileUtils
 * In Make-lang.in, fix dependency for ppVariable.o
 * Move pl1pp-parser.y to same level as pl1-parser.y 
 * Add preprocessorv2 to archive directory
 * Remove standalone option of the preprocessor pl1pp-parser.y
 * in PLIMessage.c, add function for xref list:
 * in PLIMessage.c, function showMessage, check if message contains a '\n' 
   at end of message, and only add '\n' if not.

[pl1gcc-development] Commit log 2007-01-15

[<hen...@ba...>]

More consolidation work towards the reference list.

For the complete list of changes and more details, look at the CHANGELOG file.

15-01-2007
 * In PLIParser.c, addIncludeFile, make a copy of the current active file
 * Fix "includedFrom" information for included files and preprocessor symbols    
 * Rename currentIncludeBufferElement to currentIncludeFile
 * Separated structure definitions and functions from PLIMessage.h
12-01-2007
 * From pl11.c, move function initPL1ParserParms to PLIParser.c
 * Change interface of initPLIParserParms 
 * In PLIParser.c add PLIMessage.h as dependent
 * In pl11.c removed PLIMessage.h as dependency
 * Added struct PLIParserIncludeFileList to struct PLIparserparms.
 * Move structure and functions for handling of include files out of
   pl1-scanner.l. 
 * In pl1-scanner.l, use the new PLIParser.c functions for include file
   list handling.
 * In TokenLocation.c, added new function sprintf_yyloc_short.
11-01-2007
 * Split PLIParser.h
 * Created new file PLIParserStructs.h
 * In PLIMessage added pl1/libpl1/include/TokenLocationStructs.h to 
   get the YYLTYPE.
 * In PLIParser.h, added TokenLocationStructs.h
 * In pl1-parser.y, add prototype for function pl1-parser.
 * Rename struct includeBufferListElement to struct PLIParserIncludeFile
 * Create new struct PLIParserIncludeFileList 
 * Added new code: PLIParser.c
10-01-2007
 * In pl1-parser.y, use varname without reference to type, 
 * hunting compiler warnings in pl1-parser.y
 * libpl1/src/parseDclOptionList.c: In function 'setDclElementAttr':
 * libpl1/src/parseDclStmt.c: In function 'setNewDeclareElement':
 * libpl1/src/parseDclStmt.c: In function 'mergeDeclareElements':
 * pl1/pl1pp-parser.c: In function 'pp_yyparse':
 * Figure out what is up with the makefile
 * In pl1-parser.l eliminate unused variables:
 * In IncludeFileUtils.c, use posix standard define ENOENT
 * In pl1-parser.l eliminate unused defines:
09-01-2007
 * In parseDclOptionListstruct.h, get rid of parameter as separate attribute, 
08-01-2007
 * prepare for parsing of dclchar
 * In parseDclOptionList.c, added new structure DclOptionChar:
 * In parseDclOptionList, added functions:
 struct DclOptionChar *newDclOptionChar(void);
 void showStructDclOptionChar(struct DclOptionChar *doc);
 * In parseDclOptionList.c/showDclOptionList, change print of uniontype:
 * Add initial parsing of data types for CHAR, BIT ...
 * In parseDclOptionList.c added functions to conditionally allocate dcloption 
 * Simplify parser action that test and allocates new dcl option substructure 

[pl1gcc-development] commit log 2006-12-21

[<hen...@ba...>]

the target of parsing the DECLARE statement is getting closer.
The goal for 0.0.14 is to produce a list of declare procedures and variables 
and their data types.

21-12-2006
* Rename parseDclStmt.c/newElementList to newDeclaresElementList
* Fix adding ENTRY/PROCEDURE type, to allow for proper checking...
* In addDclImplied, use the newDeclareElementList() and newDeclareElement() 
  functions, when initialising the declare elements.
20-12-2006
* add storage class to DeclareElement
* rename newDeclareElement( ..., ... ) to setNewDeclareElement( ... , ... )
* in parseDclstmt.c add newDeclareElement(void) function
18-12-2006
* in pl1-parser.y, pass the 'scanner' to any function that might use yyerror.
* in pl1-parser.y, let the parsing continue, if a duplicated DECLARE is found
  for a variable.
15-12-2006
* If a variable is already defined as parameter/implied, then use
  int setDclElementAttr(struct DclOptionList *old, struct DclOptionList *new)
  to set the attributes of the dcl element.
* Chasing a NULL error somewhere in this declare statement:
  dcl 1 yygenbb_0, %include yygenbb ;;
- found the culprit in .. pl1-parser.y/processParserStackProcedure
  The procedure entry name were only added if the OPTIONS kw is present
* And another bug, alwazs ensure current->dcl is allocated before adding to 
structure
* Lookup of names gives duplicates if a name is already defined within 
  another structure.
* pl1-parser.y/addDclDeclareElementList
  Add setting of location if the found declaration is implicit defined.
14-12-2006
* Enhance function used to find variable names within the 
  scope node structure.
* In parseDclOptionList.c/setDclElementAttr, allow old type to be UNKNOWN, 
  and just take the attributes from the new structure
* In parseDclStmt.c/showDeclareElement, add print of location
* Add TokenLocation.h as dependency to parseDclStmt.o
* Add #include "TokenLocationStructs.h" to TokenLocation.h
* An error in the include yygenbb_0 was found during the adding of variable,
12-12-2006
* in yyerror check if scanner is correctly initialised
* First cut of interface for adding a declare element structure to the
* Use addDclDeclareElementList for the parsed dcltermcommalist 	
* add location to DeclareElement structure and constructor
  struct DeclareElement *newDeclareElement( ... )
11-12-2006
* Rename function newList to newDeclareElementList
* Rename function addList2List to addElementList2List
* Add explicit/implicit indicator for dcl variables.
* Rename addDcl to addDclImplied
* Removed old declare structures from parseMiscStructs.h
* added field implied to struct DeclareElement:
* Analysing new interface for adding a declare element structure to the
  current scope node, first cut (in pl1-parser.y):
10-12-2006
* Fixed rename of structure DeclareList to DeclareElementList
06-12-2006
* Sent out a tasklist in the hope someone will bite...
  Sent to comp.lang.pl1 and pl1...@li....
	There are a number of interesting tasks related to the pl1gcc project, where 
	any help would be greatly appreciated.
	a) Error regression infrastructure
	b) Error message codes
	c) Case insensitive include name expansion
	d) Test cases
	e) Web pages
	f) Language reference manual
	g) User guide
	h) Tutorial to PL/I
	i) Frequently asked questions
	j) Internals of pl1gcc