Activity for The_Piper
-
The_Piper posted a comment on discussion Bug_Reports
Fixed, removed the word "lesser" from source, document and also from the VER command. Will be shipped with the next release. Thanks for reporting this mess!
-
LOL, somehow i have the impression you don't like TeX very much :P
-
Thanks for reporting Vince, going to fix all those warnings and errors with the next update. And yeah, haven't used TeX for a longer time also, was fun to work with it again :) Thr next release will have the missing image for TeX too..
-
Thanks for reporting Vince, going to fix all those warnings and errors with the next update. And yeah, haven't used TeX for a longer time also, was fun to work with it again :)
-
1st of may update. Some more bugfixes and a simple spread sheet (ss) macro, just to show what macros can do.
-
Update done, looks like it is working. Feel free to post bug reports here.
-
1st of may update of pipEdit, some more bugfixes. Available here: https://sourceforge.net/p/pipedit/code/HEAD/tree/ Bug reports are welcome :)
-
1st of may release - bugfixes
-
1st of may update - bugfixes
-
1st of may update - bugfixes
-
Starting 1st of may update now. Hopefully i don't break everything.....
-
Thats correct, the scroll factors arent implemented yet.
-
Update: I am still testing the editor, i am now down to one last crash which happens once in a blue moon... Two new macros will come with the next update, not really useful, but to show what macros can do, a calculator and a very simple spread sheet. I am testing the editor by writing a new COBOL preprocessor from scratch with the editor and the macros, maybe it's useful, maybe it's just fun to have :)
-
I dont think that 1.4 is fully implemented until now.
-
D'oh, thats why i love my Firefox, it always forgets some cookies or whatever... And you're right, let it be moderated, spam is not needed.
-
First release of the emulator. The source code can be found in the "Files" section.
-
First release of the emulator.
-
Sorry, got sidetracked again, but this is still on my to-do list. Going to work on it hopefully soon.
-
The brackets and preceding colon is from Micro Soft SQL server, and ditto the rest of rdb syntax used. Going by my 75 year old memory was trying to see what dbpre did with it :) That way, I would hopefully know what needed changes. Ah, okay, i have never used Micro Soft SQL server, that explains it ;) Big grief is that on the .lst and .cob dbpre, is double spacing each source line and that is odd as in Windows each line is ended by a CR,LF combo but for *nix it is only one of them LF, so what is...
-
The brackets and preceding colon is from Micro Soft SQL server, and ditto the rest of rdb syntax used. Going by my 75 year old memory was trying to see what dbpre did with it :) That way, I would hopefully know what needed changes. Ah, okay, i have never used Micro Soft SQL server, that explains it ;) Big grief is that on the .lst and .cob dbpre, is double spacing each source line and that is odd as in Windows each line is ended by a CR,LF combo but for *nix it is only one of them LF, so what is...
-
I'm looking at it right now. EXEC SQL INCLUDE has a copybook with the suffix .cpy, dbpre doenst expect that and works only with copybooks without any suffix. I'll try to make that more flexible, so both formats can be used. Comments in your source code are usually written with "*>", one comment line starts only with a single asterik which confuses dbpre. EXEC SQL BEGIN DECLARE SECTION - dbpre doesnt need that, i'll try to make dbpre to ignore that. PREPARE/EXECUTE - dbpe doenst support that right...
-
I'm looking at it right now. EXEC SQL INCLUDE has a copybook with the suffix .cpy, dbpre doenst expect that and works only with copybooks without any suffix. I'll try to make that more flexible, so both formats can be used. Comments in your source code are usually written with "*>", one comment line starts only with a single asterik which confuses dbpre. EXEC SQL BEGIN DECLARE SECTION - dbpre doesnt need that, i'll try to make dbpre to ignore that. PREPARE/EXECUTE - dbpe doenst support that right...
-
I'm looking at it right now. EXEC SQL INCLUDE has a copybook with the suffix .cpy, dbpre doenst expect that and works only with copybooks without any suffix. I'll try to make that more flexible, so both formats can be used. Comments in your source code are usually written with "*>", one comment line starts only with a single asterik which confuses dbpre. EXEC SQL BEGIN DECLARE SECTION - dbpre doesnt need that, i'll try to make dbpre to ignore that. Lets see if the next release can handle your source...
-
Hi Ian, sorry for the late reply, just found your post here.. -lmysqlclient might be MySql specific, you have to find out how to compile COBOL programs with MariaDB (sorry, i have never used MariaDB). Maybe searching the GnuCOBOL forum for MariaDB support or asking there for help is a solution https://sourceforge.net/p/gnucobol/discussion/ Your problem is not a problem of using dbpre, it is how to compile and link COBOL programs with GnuCobol and MariaDB. Piper
-
Ok, uploaded V0.4 again, no clue why all files were deleted, maybe because i once used kdesvn which crashes very often.... Tested it with the example program and it precompiles/compiles.
-
dbpre V0.4 uploaded again
-
For some unknown reasons all files of release V0.4 were gone. Uploaded them again in a new folder structure and fixed some typos in the documentation.
-
new folder structure, typos fixed
-
new folder structure
-
new folder structure
-
new folder structure
-
restored V0.4
-
oops, yes, 0.4 is empty, going to fix that soon, But you can still download a snapshot from the '"code" section.
-
Yes, Vincent, thats the latest version.
-
New release with some bugfixes, new line command "ts", new macros, def, ll, lcpy, zoomin. Updated documentation.
-
new ureplace.c function
-
Bug fixes, new macros, zoomin, ll, def, rem
-
Bug fixes, new macros
-
And while i am on it, macro development and debugging is now quite easy, another one: zoomin https://sourceforge.net/p/pipedit/blog/2021/08/macro-zoomin/
-
Macro zoomin
-
To be honest, i've never used VAR IN GROUP OF REC in my whole life, so i think, we can live without that :)
-
To be honest, i've never used VAR IN GROUP OF REC in my hole life, so i think, we can live without that :)
-
And another macro, lcpy, Locate Copybook in the $COBCPY pathes. And the def macro can now handle nested copybooks.
-
And another macro, lcpy, Locate Copybook in the $COBCPY pathes.
-
And another macro, lcpy, Locate Copybook in the $COBCPY pathes. ![(https://sourceforge.net/p/pipedit/blog/2021/07/and-another-macro---lcpy---locate-copybook/attachment/pipedit_macro_lcpy.png/thumbhttps://)]
-
And another macro, lcpy, Locate Copybook in the $COBCPY pathes.
-
And another macro - lcpy - locate copybook
-
Two new macros
-
Two new macros
-
Two new macros
-
Two new macros
-
Two new macros
-
Two new macros
-
Two new macros
-
For def macro: shouldn't it be possible to automatically position to the beginning of the current word? Yes, and same for the LL macro. Do you already handle VAR IN GROUP OF REC and definitions in copybooks? Handling copybooks is on my todo list, but i am going to handle that on my own and wont use any cobol compiler. The editor should not rely on any given cobol compiler, but should work even if no one is installed.
-
Two new macros
-
Two new macros
-
A little teaser, two new macros coming with the next release: https://sourceforge.net/p/pipedit/blog/2021/07/two-new-macros/ And i fixed some crashes, but still testing, testing, testing....
-
A little teaser, two new macros with the next release: https://sourceforge.net/p/pipedit/blog/2021/07/two-new-macros/ And i fixed some crashes, but still testing, testing, testing....
-
Two new macros
-
Two new macros
-
Two new macros
-
Two new macros
-
CHANGE and FIND, PICTURE strings
-
This now took a little bit longer than expected.. I found some bugs and some very evil crashes of the editor while using it more myself. The crashes cause a loss of the edited source code, so not very nice. With the next release some new line commands will come like "<<", ">>" and finally, "c", change. Also "ts", text split, and "tf", text float. Further a macro which can do block copy of blocks of source code, maybe. But first, get rid of the crashes of the editor.
-
This now took a little bit longer than expected.. I found some bugs and some very evil crashes of the editor while using it more myself. The crashes cause a loss of the edited source code, so not very nice. With the next release some new line commands will come like "<<", ">>" and finally, "c", change. Also "ts", text split, and, i think, it's "tj", text join, going to figure out the correct syntax later.. Further a macro which can do block copy of blocks of source code, maybe. But first, get rid...
-
There is a new version of pipEdit coming soon. it has some bugfixes, if someone wants to test it, it is already here: https://sourceforge.net/projects/pipedit/ If no one reports any bugs or problems, i am going to release it to the tools section of GnuCOBOL in a few days.
-
The editor had some issues with finding macros and the comp macro had some problems when the parameter file for a COBOL program was missing. Fixed both and macros can now return an error message to the editor and stop it from reloading the (modified) source code.
-
Bugfix for macro handling / comp macro
-
localized language support
-
English language file added, users guide updated.
-
Updated user_guide, added english langfile
-
Umm.. is that really needed? Just have a look at the german language file and change the german text to french, spanish, whatever. (English is the default, hard coded in pipEdit) But i am going to add a chapter about language files to the pipEdit_User_Guide.pdf.
-
Added german language file
-
Added german language file
-
ok, uploaded pipedit.de in folder langfiles, german language file.
-
As the subject says, Simon did some bugfixes and i added the "lic"/"license'" command. The lic/license line command will display informations of the license pipEdit uses, the Gnu lesser General Public License. Just type lic or license in the command line and press ENTER key,then press F1 to toggle the short or longer message.
-
lic/license command and users guide update
-
Sure, if someone has more language files, upload them or post a link to them in "Discussion", so I/we can add them.
-
This update has a lot of bug fixes, for example, local and global variables are working correctly now, negative numbers are now (hopefully) correctly handled. And there is now a game named "Hammurabi", which i converted from BASIC to LoLCode. It's an economic simulation, you have to run a city for 10 years, plant grain, buy and sell land and such. Maybe the first useful program ever written in lolcode :) I found hammurabi, when i had a look at tinybasic, there are too some other (old) games, like...
-
"Trying to do COBOL on the PC is not easy with all the editors out there!!!" The PC is not the problem ;) Hint: LINUX wink :) Stay safe too and good luck with COBOL!
-
Okay, it's not that easy... Just taking the source code and compiling it with gcc does not work. Maybe using PDCurses with pipEdit under Windows might work, but i dont have the time right now to try that. As an alternative, i would suggest to try "The Hessling Editor", but i see, you posted there already. Another thing for Windows i've found is this: https://github.com/Ambusy/XeditPc
-
I havent tried to compile it for Windows, but i will try it later, if i have some spare time. I will try to compile it with gcc, which comes with GnuCobol for Windows. https://arnoldtrembley.com/GnuCOBOL.htm#binaries And if i can compile it, i will upload the binary here.
-
Bugfix for INS/DEL keys.
-
Bugfix for INS/DEL keys
-
Bugfix for INS/DEL keys, now, when they are pressed, the source code is rated as changed and saved when leaving the editor. The bug was, when you edit a file and just delete (or insert) characters, the source code wouldnt be saved.
-
Bugfix for INS/DEL keys, now, when they are pressed, the source code is rated as changed and saved when leaving the editor. The bug was, when you edit a file and just delete (or insert) characters, the source code wouldt be saved.
-
-
@jklowden Yes, thats the dbpre i/we are talking about. Alan Honeyman and another person want to use it under Windows, thats the reason why i am trying to get it working under Windows. Edit: I just googled for dbpre and only found my project at sourceforge on the first page. Maybe i should sue Oracle for using my name for a precompiler, might be a nice source of income XD
-
@jklowden Yes, thats the dbpre i/we are talking about. Alan Honeyman and another person want to use it under Windows, thats the reason why i am trying to get it working under Windows.
-
Thanks @sf-mensch, thats it obviously, scrolling down on Arnolds page helps to find a 64 bit version... Going to try that later, watching the US elections right now on TV :P
-
Thanks Simon, thats it obviously, scrolling down on Arnolds page helps to find a 64 bit version... Going to try that later, watching the US elections right now on TV :P
-
Yes, thats the dbpre i/we are talking about. Alan Honeyman and another person want to use it under Windows, thats the reason why i am trying to get it working under Windows too.
-
Somehow i am stuck with that stuff and Windows... I have installed GnuCobol+gcc for Windows 10 from Arnolds page. I have installed MySQL. I can compile dbpre with gcc. I can compile cobmysqlapi.c with gcc and get an object file. I can preprocess scb files with dbpre. But when i compile the preprocessed COBOL source code with cobc i get this from ld.exe: Recognized but unhandled machine type (0x8664) in Import Library format archive I compile it this way: dbpre PCTB003B -ts=3 -I..\copybooks cobc -x...
1 >