fileref.sas / varexist.sas / dquote.sas run unmodified on Jenner#8
Open
jenner-analytics wants to merge 1 commit into
Open
fileref.sas / varexist.sas / dquote.sas run unmodified on Jenner#8jenner-analytics wants to merge 1 commit into
jenner-analytics wants to merge 1 commit into
Conversation
Adds jenner-check/ with self-contained compatibility bundles for dquote/squote, varexist, and fileref, each pinned against a captured passing run, plus the shell runner and its README.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Jenneranalytics.com provides an API that runs SAS code, with support for more than 200 SAS procedures. You can also use it with AI assistants in a collaborative workspace. It's available for Mac on the Apple App Store, and by license for Windows and Linux.
We support the larger community by
(1) increasing access to SAS-compatible systems,
(2) by providing test coverage and a test coverage framework to public SAS repos in order to encourage the use of best practices in software engineering.
Your fileref.sas runs on Jenner unmodified — this PR adds a small compatibility bundle so you can see for yourself. It's the test we wrote for your macro library, shared in case it's useful, and was assembled with AI assistance as is most code in modern businesses today.
fileref.sas's layered validation is what stood out most reading through this — it doesn't just delegate to the nativeFILEREF()function, it front-loads the three ways a fileref argument can be nonsense (blank, over 8 characters, not a valid V7 name) and short-circuits all of them to the same "not usable" result before ever calling into SCL. That's a small design choice, but it's the kind of defensive shaping that separates a library people actually reuse from one they have to read the source of first. The header-comment usage examples throughout the library (the%parmvwalkthrough especially) read like documentation written for someone other than the author, which is rarer than it should be.jenner-check/is a self-contained, optional bundle: a byte-identical copy of three of your macros (dquote/squote,varexist,fileref), a small caller exercising each against inline sample data, the captured output of that run, and a runner script. Nothing outsidejenner-check/is touched, nothing executes on merge, and there are no workflow files or hooks.Check out this PR's branch and run from the repo root —
jenner-check/only exists on this branch:cd jenner-check && ./run_jenner.sh --allre-runs all three bundles and checks the result against each one's pinnedexpected.json. The hosted API is free to try, no signup required; full API reference: the docs.Only the SAS source of the script being run (plus a two-line autoexec) is uploaded to
api.jenneranalytics.com, which runs it and returns the log and listing — no data files are read or uploaded, so anything sitting next to a script stays on your machine, and nothing is sent unless you run a command yourself. It's the same exposure as pasting a snippet into any hosted tool; if a script embeds sensitive values inline, that's the one thing worth reviewing before you paste it in.Merge it, close it, or ignore it — no response expected, and we won't open further PRs in this repo. To opt out for good, mention
no-more-prsin any comment here, or open an issue titledjenner-check: opt out.Lawrence W. Sinclair
CEO / Jenner Analytics Ltd
linkedin.com/in/lwsinclair/