Tweaks to poetry annotations?
Cowan
Love the 'literary' annotations but have a few concerns that they do
not appropriately support the classical forms.
Firstly, Feet enum clearly needs DACTYLIC added, that's a no-brainer.
Next, a problem with @Meter: you just can't quite make it restrictive
enough. Sure, you can make the code dictate the possible feet the code/
verse is written in, but not the length of the line itself, which is
crucial for any destined-to-be-classic code poetry.
For truly flowing code, we really need:
@Meter(feet=TROCHAIC, measure=TETRAMETER)
public static final double
finalizeTheMonthlyBudget(
MonthName target = AUGUST;
auditLog.writeln(target);
checkForWriteoffChargesPending();
writeResultToDataStorage();
... etc etc ...
right?
Measure values are MONOMETER, DIMETER, TRIMETER, TETRAMETER,
PENTAMETER, HEXAMETER, HEPTAMETER, OCTOMETER...
Also, as a long-time limerick fan (and contributor to http://oedilf.com/
) I find the CLEAR bias shown towards Haiku as a verse form in this
library to be somewhat disturbing. What's wrong with
@Limerick void scoreResult() {
SearchResult whatIFound = hit;
whatIFound.adjustForBestFit();
whatIFound.setScore(
new SearchScore(94));
searchTransaction.safelyCommit();
}
?
Perhaps @Verse(HAIKU), with a VerseForm enum of {HAIKU, LIMERICK,
SONNET, CLERIHEW, DOUBLE_DACTYL, BURMA_SHAVE} would be less obviously
biased against the noble form of the limerick.
Paul
Leo Deegan
--
To unsubscribe, reply using "remove me" as the subject.
Cowan
On Apr 2, 10:11 am, Leo Deegan <leodee...@google.com> wrote:
> Not including @Limerick is a clear oversight. Regarding @Haiku and @Limerick
> vs. @Verse(HAIKU) and @Verse(LIMERICK), allow me to suggest we ponder the
> aesthetics of each proposal. In my opinion, the latter is a more logical
> grouping, but the former is more aesthetically pleasing. Given poetry is
> often about extracting great meaning from a paucity of words, I'd lean
> towards a verse package with @Haiku, @Limerick, @Sonnet, etc. What are your
> thoughts on the matter?
+1. Agree that it looks much nicer. And it's all about the
aesthetics... (@Sonnet(renderIn="Zapf Chancery")? Naaah...)
> Incidentally great examples. Your limerick, in particular, is laudable.
Thanks, I was rather proud of the limerick. Feel free to use if you
add an @Limeick annotation.
Cheers,
Paul
Leo Deegan
Paul
Cowan
On Apr 2, 10:28 am, Leo Deegan <leodee...@google.com> wrote:
> Superb, I'll make the changes and put your limerick in the Javadoc. I was
> thinking of having a @Visionary annotation to credit the originator. Are you
> opposed to your name showing up in the code?
Hell no.
If this is the biggest public embarrassment and evidence of
timewasting that appears in my name on the internet, I'll die very
happy (and very surprised).
Go for it.
Leo Deegan
--
Cowan
On Apr 2, 10:50 am, Leo Deegan <leodee...@google.com> wrote:
> Eheheh. I might have misunderstood you (I read that as a double negative:
> "hell no I'm not opposed"), so just to make sure I'm hearing you correctly,
> are you okay with @Visionary("Paul Cowen") showing up in these new
> annotation classes?
Sorry for the confusion. Yes, it's fine. Go for it. But it's "Cowan"
with an "a". :)
Paul
Leo Deegan
Leo Deegan
Paul Cowan
> All work done, added to version 1.0.1. Nice suggestions, thanks Paul.
Thanks Leo. Minor nitpick: while my surname is spelled correctly in the
@Visionary annotations for the .verse package, my first name isn't --
it's Paul, not Peter. Oops. :)
If it's helpful, I've come up with examples for @BurmaShave and
@DoubleDactyl which you might like for the Javadoc:
@BurmaShave
public void handleError() {
if (jobIsDead()
|| connIsDropped()) {
{
logAWarning();
thread.stop();
// Burma Shave.
}
}
@DoubleDactyl
public void createNewTractor() {
tractoryFactory
.tractorConfigurer()
.setTractorPaintjob(
A_BRIGHT_SHINY_RED
);
saveTheNewTractor(
AUTOTRANSACTIONALLY);
driveTheNewTractorIn
(new WorkerThread());
}
That second one was HARD. Sonnets and Clerihews will have to wait. :)
Cheers,
Peter^H^H^H^H^HPaul
