Labels Milestones

Add example for vec_permxor #34

Merged

ThinkOpenly merged 1 commits from vec_permxor into master 4 years ago

Conversation 6 Commits 1 Files Changed 1

ThinkOpenly commented 4 years ago (Migrated from github.com)

vec_permxor is complex enough to warrant an example.

The table used is very wide. I squeezed it more by changing the names
of index1 and index2 to x and y, respectively.

Note: The table may still be too wide, as some additional warnings are
now generated during mvn generate-sources:

WARNING: Line 1 of a paragraph overflows the available area by more than 50 points. (See position 1:-1)
Apr 30, 2020 8:44:03 PM org.apache.fop.events.LoggingEventListener processEvent
WARNING: Line 1 of a paragraph overflows the available area by 468 millipoints. (See position 14259:-1)
Apr 30, 2020 8:44:03 PM org.apache.fop.events.LoggingEventListener processEvent
...
WARNING: span="inherit" on fo:block, but no explicit value found on the parent FO.

Fixes #20.

Signed-off-by: Paul A. Clarke pc@us.ibm.com

`vec_permxor` is complex enough to warrant an example. The table used is very wide. I squeezed it more by changing the names of `index1` and `index2` to `x` and `y`, respectively. Note: The table may still be too wide, as some additional warnings are now generated during `mvn generate-sources`: ``` WARNING: Line 1 of a paragraph overflows the available area by more than 50 points. (See position 1:-1) Apr 30, 2020 8:44:03 PM org.apache.fop.events.LoggingEventListener processEvent WARNING: Line 1 of a paragraph overflows the available area by 468 millipoints. (See position 14259:-1) Apr 30, 2020 8:44:03 PM org.apache.fop.events.LoggingEventListener processEvent ... WARNING: span="inherit" on fo:block, but no explicit value found on the parent FO. ``` Fixes #20. Signed-off-by: Paul A. Clarke <pc@us.ibm.com>

ThinkOpenly commented 4 years ago (Migrated from github.com)

Web version:

PDF:

Web version:  PDF: 

wschmidt-ibm commented 4 years ago (Migrated from github.com)

a_x ^ a_y is wrong. Should be a_x ^ b_y, correct?

Anyway, I don't like having that in the table. Would prefer the row just say r.

a_x ^ a_y is wrong. Should be a_x ^ b_y, correct? Anyway, I don't like having that in the table. Would prefer the row just say **r**.

👍 1

wschmidt-ibm commented 4 years ago (Migrated from github.com)

Have you verified the output with a test compiled with gcc?

Have you verified the output with a test compiled with gcc?

👍 1

ThinkOpenly commented 4 years ago (Migrated from github.com)

I did verify with GCC.
I have now removed the "a_x ^ b_y" line (and yes, it was supposed to be b_y, now moot.)

Fix is ready for review.

I did verify with GCC. I have now removed the "a_x ^ b_y" line (and yes, it was supposed to be **b**_y, now moot.)  Fix is ready for review.

wschmidt-ibm commented 4 years ago (Migrated from github.com)

Looks good, thanks!

Looks good, thanks!

wschmidt-ibm commented 4 years ago (Migrated from github.com)

Will rebase and merge shortly after I finish pushing something I'm working on.

Will rebase and merge shortly after I finish pushing something I'm working on.

The pull request has been merged as 8c13a59ceb.

You can also view command line instructions.

Step 1:

From your project repository, check out a new branch and test the changes.

git checkout -b vec_permxor master

git pull origin vec_permxor

Step 2:

Merge the changes and update on Gitea.

git checkout master

git merge --no-ff vec_permxor

git push origin master

Sign in to join this conversation.

Reviewers

Request review

No reviewers

Labels

Apply labels

Clear labels   

bug

  

duplicate

  

enhancement

  

future

Deferred to a future release   

good first issue

  

help wanted

  

invalid

  

P1

Must be incorporated into next document publish   

P2

Desirable for incorporation into next document publish   

P3

Low priority for next document publish   

question

  

wontfix

No Label

bug

duplicate

enhancement

future

good first issue

help wanted

invalid

P1

P2

P3

question

wontfix

Milestone

Set milestone

Clear milestone

No items

No Milestone

Projects

Set Project

Clear projects

No project

Assignees

Assign users

Clear assignees

No Assignees

1 Participants

Notifications

Subscribe

Due Date

The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: systemsoftware/Programming-Guides#34

Write Preview

Loading…

Cancel

Save

There is no content yet.