New Version of PragmARC.Text_IO

New Version of PragmARC.Text_IO

[PragmAda Software Engineering]

The initial version of this was adding an extra (native) EOL to files 
when they were closed. This has now been corrected. The package 
specification has changed somewhat in the process.

The PragmAda Reusable Components are available from the PragmAda web 
site or from

https://github.com/jrcarter/PragmARC

-- 
Jeffrey R. Carter, President
PragmAda Software Engineering
pragmada.x10hosting.com


--- news://freenews.netfront.net/ - complaints: news@netfront.net ---

Re: New Version of PragmARC.Text_IO

[jrmarino]

Hi Jeff,
Thanks for moving this to Github.  It made it easy for me to add PragmARCs to FreeBSD ports:
http://www.freshports.org/devel/pragmarcs/

I turned it into a standard library and installed a gpr file in the standard location for ports.

Some observations:
1) You *really* need some documentation in the actual repository (more than just list each package with a one-line description, which isn't even in the repo).  Documentation should be installed.

2) It would really help to use github's "release" mechanism by tagging.  Since there was no release info, I had to invent a versioning scheme and I picked a ISO8601 date scheme and a git hash tag.  It would provide more re-ensurance to correspond to actual releases instead of random tags.

3) it built very cleanly with gcc5 FSF. there was only one warning in the whole thing (unreachable code on line 108 of the menu_handler)

Hopefully pragmarcs will get more exposure now that it will be provided as a prebuilt library.

Thanks,
John

Re: New Version of PragmARC.Text_IO

[Jeffrey R. Carter]

On 03/04/2016 08:05 AM, jrmarino wrote:
> Hi Jeff,
> Thanks for moving this to Github.  It made it easy for me to add PragmARCs to FreeBSD ports:
> http://www.freshports.org/devel/pragmarcs/

I'm glad this helped you. However, I haven't moved them to GitHub; rather, I've
provided an alternative access path to the code through GitHub. This was
primarily to assist the distribution of some Gnoga demo code.

> Some observations:
> 1) You *really* need some documentation in the actual repository (more than just list each package with a one-line description, which isn't even in the repo).  Documentation should be installed.

There are 2 questions that apply here: which version of the PragmARCs you're
referring to, and what you mean by repository. The Ada-95 version comes with a
set of test programs and some documentation, all provided through the main site
for the components, pragmada.x10hosting.com. These are not part of the
components' code, and so not found at GitHub. But the primary documentation for
a pkg is in its spec.

The version that uses features of ISO/IEC 8652:2007 is labeled "beta" and is
only the source code. The test programs and documentation for the Ada-95 version
may be useful as a starting point for a better understanding of this version
than provided by the pkg specs. Someday I might make the effort to convert the
test programs and add some documentation to this version and move it out of beta
status.

> 2) It would really help to use github's "release" mechanism by tagging.  Since there was no release info, I had to invent a versioning scheme and I picked a ISO8601 date scheme and a git hash tag.  It would provide more re-ensurance to correspond to actual releases instead of random tags.

The beta version for ISO/IEC 8652:2007 comes as ZIP files with the year and
month of the release as part of the file name. The branch at GitHub that
reflects this version contains the most recent of these. There's been no change
to the Ada-95 version for several years so it exists as a single, undated ZIP file.

> 3) it built very cleanly with gcc5 FSF. there was only one warning in the whole thing (unreachable code on line 108 of the menu_handler)

Interesting. IIRC, that line is in there because of a compiler warning that
there was no return statement there.

-- 
Jeff Carter
"The men get one hot meal a day: a bowl of steam."
Take the Money and Run
145

Re: New Version of PragmARC.Text_IO

[jrmarino]

On Friday, March 4, 2016 at 7:36:28 PM UTC+1, Jeffrey R. Carter wrote:
> I'm glad this helped you. However, I haven't moved them to GitHub; rather, I've
> provided an alternative access path to the code through GitHub. 

As long as it's keep it sync with the real repository, that's a synmantec issue; the latest code is available via github.  The movement had the immediate benefit of making it suitable for bringing into ports (see below for the problem that existed before).  


> There are 2 questions that apply here: which version of the PragmARCs you're
> referring to, and what you mean by repository. The Ada-95 version comes with a
> set of test programs and some documentation, all provided through the main site
> for the components, pragmada.x10hosting.com. These are not part of the
> components' code, and so not found at GitHub. But the primary documentation for
> a pkg is in its spec.

by "repository" i mean the entire contents of PramgARC in github.
I could guess documentation in some for exists in specification or body of the package, but when people say "documentation" they mean something that's installed separately, something they can review without looking at the code itself.  I was basically stating an opinion that documentation as I just defined it doesn't exist in repository (and you say not at all) and that PragmARCs would be greatly improved with such documention.  It's just an opinion.  If it doesn't exist, there's nothing more I (as a packager) can do about it.

Hoewver, I had to struggle to even create the package description because that didn't exist, but people have to know what the package does or they won't even try to install it.  (see freshports URL for the description I made)


> The beta version for ISO/IEC 8652:2007 comes as ZIP files with the year and
> month of the release as part of the file name. The branch at GitHub that
> reflects this version contains the most recent of these. There's been no change
> to the Ada-95 version for several years so it exists as a single, undated ZIP file.

It should be trivial to tag github repository in the exact commits corresponding to tarballs so that obtaining code via tarball or via github results in same content.  It would not take long and I think it's useful, expecially for OS packagers.

I just looked at PragmARCs in any kind of detail yesterday.  I packaged it to help others discover and use it, and to help you get exposure for it.  I didn't directly benefit.  The duplication to github definitely was beneficial for porting it though.

New Version of PragmARC.Text_IO

[PragmAda Software Engineering]

There's a new version of package PragmARC.Text_IO available. This
corrects an error in Skip_Line and changes the line terminator used for
output from a single value used for all files to a value per file,
specified when the file is opened or created.

The PragmAda Reusable Components are available from the web site or from

https://github.com/jrcarter/PragmARC

-- 
Jeffrey R. Carter, President
PragmAda Software Engineering
pragmada.x10hosting.com
pragmada.tk


--- news://freenews.netfront.net/ - complaints: news@netfront.net ---